Re: Avoid full GIN index scan when possible

Поиск
Список
Период
Сортировка
От Alexander Korotkov
Тема Re: Avoid full GIN index scan when possible
Дата
Msg-id CAPpHfdttREdy0H9ovJjcd5UUu1my6TS8GRNRuKpL2dTDt8o2wQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Avoid full GIN index scan when possible  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Ответы Re: Avoid full GIN index scan when possible
Список pgsql-hackers
On Fri, Jan 10, 2020 at 7:36 PM Alexander Korotkov
<a.korotkov@postgrespro.ru> wrote:
>
> On Fri, Jan 10, 2020 at 6:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> Alexander Korotkov <a.korotkov@postgrespro.ru> writes:
>> > So, I think v10 is a version of patch, which can be committed after
>> > some cleanup.  And we can try doing better nulls handling in a separate
>> > patch.
>>
>> The cfbot reports that this doesn't pass regression testing.
>> I haven't looked into why not.
>
>
> Thank you for noticing.  I'll take care of it.


In the v10 I've fixed a bug with nulls handling, but it appears that
test contained wrong expected result.  I've modified this test so that
it directly compares sequential scan results with bitmap indexscan
results.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Assert failure due to "drop schema pg_temp_3 cascade" fortemporary tables and \d+ is not showing any info after drooping temp tableschema
Следующее
От: nuko yokohama
Дата:
Сообщение: Re: Implementing Incremental View Maintenance