From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Nabil Sayegh <postgresql(at)e-trolley(dot)de> |
Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: 7.4 dramatically slower than 7.3? |
Date: | 2004-04-06 19:12:57 |
Message-ID: | 420.1081278777@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Nabil Sayegh <postgresql(at)e-trolley(dot)de> writes:
> Stephan Szabo wrote:
>> One other possibility is that the planning is taking a really long time.
>> How long do explain (non-analyze) on the two systems take? And how many
>> joins are there precisely?
> 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?
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/static/explicit-joins.html
and experiment with altering JOIN_COLLAPSE_LIMIT (and/or reordering the
joins in your query).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PaulS | 2004-04-06 19:14:05 | Re: dotnet stored procedures with postgresql |
Previous Message | Manfred Koroschetz | 2004-04-06 18:37:21 | Re: Help for MSSQL "Compute" equivalent in Postgres |