| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Schuller | 2008-06-30 15:34:35 | Re: VACUUM ANALYZE blocking both reads and writes to a table |
| Previous Message | Alvaro Herrera | 2008-06-30 15:25:15 | Re: VACUUM ANALYZE blocking both reads and writes to a table |