From: | hubert depesz lubaczewski <depesz(at)depesz(dot)pl> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SQL question - problem with INTERSECT |
Date: | 2000-11-02 13:44:49 |
Message-ID: | 20001102144449.A7284@gruby |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Nov 02, 2000 at 06:50:07AM -0500, Keith L. Musser wrote:
> > upper(a.word) = 'JIM' or upper(a.word) = 'JONES'
> > upper(s.word) = 'HELLO' or upper(s.word) = 'THERE'
> Interesting possibility. Unfortunately, the outer select ends up being
> a sequential scan over the entire messages table, where at each row the
> message id is looked up sequentially in the nested query.
did you try my quesry with "upper's" in it?
if so then is your index on a.word or on upper(a.word)?
try making functional indies, and of course vacuum'im tables to make indices
work.
this query *should* work with indices.
depesz
--
hubert depesz lubaczewski
------------------------------------------------------------------------
najwspanialszą rzeczą jaką dało nam nowoczesne społeczeństwo,
jest niesamowita wręcz łatwość unikania kontaktów z nim ...
From | Date | Subject | |
---|---|---|---|
Next Message | J. Burke | 2000-11-02 15:23:39 | where to find postgresql jobs in the Washington, DC area?? |
Previous Message | Andy Corteen | 2000-11-02 13:22:18 | Re[2]: autostart postgresql |