> I'm leaning towards removing RECHECK because it'll allow simplification
I vote to do it.

> I seem to recall that you had some plans for other incompatible changes
> in the call conventions for GIST/GIN support functions, too. If
Right now we suggest only new feature which just extent interface. Gregory
suggested to split compare method to two methods and I'm intending to do
it.

--
Teodor Sigaev Email: teodor@sigaev.ru
WWW: http://www.sigaev.ru


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

I've committed changes that move the determination of whether recheck is
required into the index AMs. Right now, GIST and GIN just always set
the recheck flag to TRUE. Obviously that control should be pushed down
to the opclass consistent() functions, but I don't know that code well
enough to be clear on exactly what should happen. Are you willing to
do that part?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers