From: | Coronach <coronach(at)hill-b-073(dot)resnet(dot)purdue(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev) |
Subject: | Re: [HACKERS] psql nested queries with 2000+ records |
Date: | 1998-03-21 06:12:07 |
Message-ID: | 3.0.5.32.19980321011207.007eb100@diety.conclave.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>select * into games2 from games;
amusements=> select * into games2 from games;
ERROR: parser: parse error at or near "games2"
But, I just dumped it and changed a few things to fit the scenario...
>explain select name from games where name in (select name from games2 where
>name like 'A%');
amusements=> explain select name from games where name in (select name from
game
s2 where name like 'A%');
NOTICE: QUERY PLAN:
Seq Scan on games (cost=207.95 size=446 width=12)
SubPlan
-> Seq Scan on games2 (cost=10.23 size=1 width=12)
EXPLAIN
Upon execution of the query, it still took quite a long time.
>causing the problem. I assume you have run vacuum and vacuum analyze.
Yep, ran vacuum on it and also had it work with newly generated databases too.
Any other suggestions would be welcome, thanks
-Coronach(at)hill-b-073(dot)resnet(dot)purdue(dot)edu
From | Date | Subject | |
---|---|---|---|
Next Message | Luuk de Boer | 1998-03-21 10:38:35 | Re: [HACKERS] Re: [QUESTIONS] MySQL benchmark page |
Previous Message | Bruce Momjian | 1998-03-21 05:34:59 | 6.3p1 CHANGES |