Stephan Szabo wrote:

Yeah, that seems to be it.
It takes ~
(real) 3.776s on 7.4
(real) 0.082s on 7.3
measured with bash/time but shouldn't make a difference

So the plan is actually better but takes much longer to ... plan, right?

--
e-Trolley Sayegh & John, Nabil Sayegh
Tel.: 0700 etrolley /// 0700 38765539
Fax.: +49 69 8299381-8
PGP : http://www.e-trolley.de

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

On Tue, 6 Apr 2004, Nabil Sayegh wrote:

Yes. You might want to see if lowering join_collapse_limit helps any, I'd
suggest trying 0 first and then incrementing it.


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Nabil Sayegh <postgresql (AT) e-trolley (DOT) de> writes:
Right. In 7.3 your use of JOIN syntax limited the planner's search for
good plans; in 7.4 it doesn't do so (by default anyway). You may care
to read http://www.postgresql.org/docs/7.4/s...cit-joins.html
and experiment with altering JOIN_COLLAPSE_LIMIT (and/or reordering the
joins in your query).

regards, tom lane

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

Tom Lane wrote:
Thx all, I'll try that
--
e-Trolley Sayegh & John, Nabil Sayegh
Tel.: 0700 etrolley /// 0700 38765539
Fax.: +49 69 8299381-8
PGP : http://www.e-trolley.de

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