| From: | "Ian Harding" <ianh(at)tpchd(dot)org> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org>, <ianh(at)tpchd(dot)org> |
| Subject: | Re: Nested Loop WAS: VACUUM ANALYZE makes things |
| Date: | 2002-04-12 21:09:15 |
| Message-ID: | scb6eb03.005@mail.tpchd.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
<heavy sigh> I meant enable_nestloop.... It seems the Merge Join the optimizer came up with before vacuum analyze was the right answer in this case.
>>> "Ian Harding" <ianh(at)tpchd(dot)org> 04/12/02 01:43PM >>>
Doh! I set enable_seqscan = off and things are snappy again.
Same problem though, how can I fix the query so the optimizer comes to the same conclusion?
Thanks,
Ian A. Harding
Programmer/Analyst II
Tacoma-Pierce County Health Department
(253) 798-3549
mailto: iharding(at)tpchd(dot)org
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-12 21:12:47 | Re: Nested Loop WAS: VACUUM ANALYZE makes things worse! |
| Previous Message | Tom Lane | 2002-04-12 20:47:30 | Re: Critical performance problems on large databases |