Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Allow GIN's extractQuery method to signal that nothing can

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Allow GIN's extractQuery method to signal that nothing can
Date: 2007-01-31 16:46:59
Message-ID: 45C0C803.6010504@sigaev.ru (view raw or flat)
Thread:
Lists: pgsql-committers
> 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

pgsql-committers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group