Re: [PATCH] fix GIN index search sometimes losing results - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] fix GIN index search sometimes losing results
Date
Msg-id 856353.1593707640@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] fix GIN index search sometimes losing results  (Pavel Borisov <pashkin.elfe@gmail.com>)
Responses Re: [PATCH] fix GIN index search sometimes losing results
List pgsql-hackers
Pavel Borisov <pashkin.elfe@gmail.com> writes:
> чт, 2 июл. 2020 г. в 19:38, Artur Zakirov <zaartur@gmail.com>:
>> So it seems we are losing some results with RUM as well.

> For me it is 100% predictable that unmodified RUM is still losing results
> as it is still using binary callback.

Right, that's in line with what I expected as well.

> The main my goal of saving binary legacy callback is that side callers like
> RUM will not break immediately but remain in
> existing state (i.e. losing results in some queries).

I don't really see why that should be a goal here.  I think a forced
compile error, calling attention to the fact that there's something
to fix, is a good thing as long as we do it in a major release.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jaka Jančar
Date:
Subject: Sync vs Flush
Next
From: Dave Cramer
Date:
Subject: why do we allow people to create a publication before setting wal_leve