Re: [PATCH] Check that index can return in get_actual_variable_range()

Поиск
Список
Период
Сортировка
От Maxime Schoemans
Тема Re: [PATCH] Check that index can return in get_actual_variable_range()
Дата
Msg-id 9A1BC418-94D4-42DA-942A-0E38383F78CB@enterprisedb.com
обсуждение исходный текст
Ответ на Re: [PATCH] Check that index can return in get_actual_variable_range()  (Aleksander Alekseev <aleksander@tigerdata.com>)
Список pgsql-hackers
On 19 Sep 2025, at 10:20, Aleksander Alekseev <aleksander@tigerdata.com>
wrote:

> Yes, this is how we typically test cases like this. IMO adding a test
> module would be helpful. It can be reused for other scenarios.

Here is an updated patch set.
- 0001 is unchanged.
- 0002 contains the module that tests the correct behavior of
get_actual_variable_range for non-returning ordering indices.
It contains a copy of the btree handler function with its index-only
capabilities removed. If you apply patch 0002 on master without 0001,
you will see that the test returns an error (ERROR:  no data returned
for index-only scan) as it tries to use the index in
get_actual_variable_range, which shouldn’t be the case.

Best,
Maxime Schoemans


Вложения

В списке pgsql-hackers по дате отправления: