> If you're going to support operators that could allow every tuple to

Right now it's a 'contains', 'contained by' operations for arrays.

> match, then I think you had better find a way to allow a full index scan
> within GIN.  Because the above does not fix the problem, it's only a
> very crude band-aid; you *cannot* assume that you'll always have Consts
> to look at.

Ok, I'll remove that.

-- 
Teodor Sigaev                                   E-mail: teodor(at)sigaev(dot)ru
                                                    WWW: http://www.sigaev.ru/

In response to

• Re: pgsql: Allow GIN's extractQuery method to signal that nothing can at 2007-01-31 16:37:53 from Tom Lane

pgsql-committers by date

Next:	From: Teodor Sigaev	Date: 2007-01-31 16:54:52
	Subject: pgsql: Revert gincostestimate changes.
Previous:	From: Tom Lane	Date: 2007-01-31 16:37:53
	Subject: Re: pgsql: Allow GIN's extractQuery method to signal that nothing can