Re: Nested Loop WAS: VACUUM ANALYZE makes things - Mailing list pgsql-general

From Ian Harding
Subject Re: Nested Loop WAS: VACUUM ANALYZE makes things
Date
Msg-id scb6eb03.005@mail.tpchd.org
Whole thread Raw
List pgsql-general
<heavy sigh> I meant enable_nestloop.... It seems the Merge Join the optimizer came up with before vacuum analyze was
theright answer in this case. 

>>> "Ian Harding" <ianh@tpchd.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@tpchd.org


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Critical performance problems on large databases
Next
From: Tom Lane
Date:
Subject: Re: Nested Loop WAS: VACUUM ANALYZE makes things worse!