At 11:31 PM 7/13/03 -0300, Chris Bowlby wrote:
Woops, this might not go through via the address I used :> (not
subscribed with that address)..
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
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
> > 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'). Th
Steve Wampler kirjutas P, 13.07.2003 kell 23:46:
> 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]
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 f
> select * from attributes_table where id in (select id from
> attributes where (name='obsid') and (value='oid00066'));
Can you convert it into a join? 'where in' clauses tend to slow pgsql
down.
--
Mike Nolan
---(end of broadcast)---
TIP
> 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 i
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:
Background:
RH 8.0 dual-CPU machine (1.2GHz athlon)
Postgresql 7.2
1GB ram
(Machine is dedi
