Re: [HACKERS] psql nested queries with 2000+ records

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: vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev), hackers(at)postgreSQL(dot)org (PostgreSQL-development)
Subject: Re: [HACKERS] psql nested queries with 2000+ records
Date: 1998-03-22 04:21:39
Message-ID: 3.0.5.32.19980321232139.007b4da0@diety.conclave.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Aparently, the postgresql server was moved from the BSDI box to a linux
2.0.30 box, so the numbers that where given where not from the bsdi box. So
now I am doing the queries personally. I'm sorry for the run around.

This is the responce from the explain on the BSDI 3.1 box.

amusements=> explain select name from games where name in (select name from
game
s where name like 'A%');
NOTICE: QUERY PLAN:

Seq Scan on games (cost=0.00 size=0 width=12)
SubPlan
-> Seq Scan on games (cost=0.00 size=0 width=12)

EXPLAIN

amusements=> explain select name from games where name in (select name from
game
s2 where mfr = '');
NOTICE: QUERY PLAN:

Seq Scan on games (cost=0.00 size=0 width=12)
SubPlan
-> Seq Scan on games2 (cost=0.00 size=0 width=12)

EXPLAIN

amusements=> explain select * from games where mfr = '';
NOTICE: QUERY PLAN:

Seq Scan on games (cost=0.00 size=0 width=160)

EXPLAIN

Once again, I appologize for this misinformation and hope this sheds some
light to the original problem. I'm making a note to change permissions on
who can do what from now on.

On a side note, the query was done on the 2.0.30 box in 5 minutes compared
to the BSDI box at 15+.

-Coronach(at)hill-b-073(dot)resnet(dot)purdue(dot)edu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc Howard Zuckman 1998-03-22 04:57:51 Re: [HACKERS] patch for memory overrun on Linux(i386)
Previous Message Bruce Momjian 1998-03-22 04:03:41 Re: [HACKERS] Re: sched_yield()