From: Chris Bowlby <chris@pgsql.com>
To: Steve Wampler <swampler@noao.edu>
To: pgsql-performance@postgresql.org
Subject: Re: Improving a simple query?
Date: Sun, 13 Jul 2003 23:31:01 -0300
Message-ID: <5.2.1.1.0.20030713232822.00a076c0@mail.hub.org> (raw)
In-Reply-To: <20030713204610.GA18123@weaver.tuc.noao.edu>
References: <49293.192.168.1.32.1058123357.squirrel@mainbox.archonet.com>
<1058119515.23012.114.camel@weaver.tuc.noao.edu>
<49293.192.168.1.32.1058123357.squirrel@mainbox.archonet.com>
At 01:46 PM 7/13/03 -0700, Steve Wampler wrote:
The following left join should work if I've done my select right, you
might want to play with a left versus right to see which will give you a
better result, but this query should help:
SELECT * FROM attributes_table att LEFT JOIN attributes at ON (at.name =
'obsid' AND at.value = 'oid00066') WHERE att.id = at.id;
>On Sun, Jul 13, 2003 at 08:09:17PM +0100, Richard Huxton wrote:
> > > I'm not an SQL or PostgreSQL expert.
> > >
> > > I'm getting abysmal performance on a nested query and
> > > need some help on finding ways to improve the performance:
> > [snip]
> > > select * from attributes_table where id in (select id from
> > > attributes where (name='obsid') and (value='oid00066'));
> >
> > This is the classic IN problem (much improved in 7.4 dev I believe). The
> > recommended approach is to rewrite the query as an EXISTS form if
> > possible. See the mailing list archives for plenty of examples.
> >
> > Could you not rewrite this as a simple join though?
>
>Hmmm, I don't see how. Then again, I'm pretty much the village
>idiot w.r.t. SQL...
>
>The inner select is locating a set of (2049) ids (actually from
>the same table, since 'attributes' is just a view into
>'attributes_table'). The outer select is then locating all
>records (~30-40K) that have any of those ids. Is that really
>something a JOIN could be used for?
>
>-Steve
>--
>Steve Wampler -- swampler@noao.edu
>Quantum materiae materietur marmota monax si marmota
> monax materiam possit materiari?
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: chris@pgsql.com, swampler@noao.edu
Subject: Re: Improving a simple query?
In-Reply-To: <5.2.1.1.0.20030713232822.00a076c0@mail.hub.org>
References: <49293.192.168.1.32.1058123357.squirrel@mainbox.archonet.com> <1058119515.23012.114.camel@weaver.tuc.noao.edu> <5.2.1.1.0.20030713232822.00a076c0@mail.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox