Skip site navigation (1) Skip section navigation (2)

Re: sequence scan problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Beaver <john(dot)e(dot)beaver(at)gmail(dot)com>
Cc: Jeremy Harris <jgh(at)wizmail(dot)org>, Pgsql-Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: sequence scan problem
Date: 2008-06-30 15:25:55
Message-ID: 28999.1214839555@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
John Beaver <john(dot)e(dot)beaver(at)gmail(dot)com> writes:
> Ok, here's the explain analyze result. Again, this is Postgres 8.3.3 and 
> I vacuumed-analyzed both tables directly after they were created.

>  Merge Join  (cost=1399203593.41..6702491234.74 rows=352770803726 
> width=22) (actual time=6370194.467..22991303.434 rows=15610535128 loops=1)
                                                        ^^^^^^^^^^^

Weren't you saying that only 50 rows should be returned?  I'm thinking
the real problem here is pilot error: you missed out a needed join
condition or something.  SQL will happily execute underconstrained
queries ...

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Peter SchullerDate: 2008-06-30 15:34:35
Subject: Re: VACUUM ANALYZE blocking both reads and writes to atable
Previous:From: Alvaro HerreraDate: 2008-06-30 15:25:15
Subject: Re: VACUUM ANALYZE blocking both reads and writes to atable

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group