Re: Remove lossy-operator RECHECK flag?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Teodor Sigaev" <teodor(at)sigaev(dot)ru>
Cc: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Remove lossy-operator RECHECK flag?
Date: 2008-04-13 19:21:06
Message-ID: 22674.1208114466@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-04-13 20:03:20 Re: printTable API (was: Show INHERIT in \du)
Previous Message Bruce Momjian 2008-04-13 18:12:10 Re: [HACKERS] Terminating a backend

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2008-04-13 20:03:20 Re: printTable API (was: Show INHERIT in \du)
Previous Message Gavin Sherry 2008-04-13 18:24:21 Re: datum passed to macro which expects a pointer