From: Kris Jurka <books@ejurka.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Eric Brown <bigwhitecow@hotmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: severe performance issue with planner
Date: Sat, 13 Mar 2004 22:48:01 -0500 (EST)
Message-ID: <Pine.BSO.4.56.0403132240261.491@leary.csoft.net> (raw)
In-Reply-To: <4726.1079064433@sss.pgh.pa.us>
References: <BAY13-F54DwKAYzTkuA00017c9b@hotmail.com>
<4726.1079064433@sss.pgh.pa.us>
On Thu, 11 Mar 2004, Tom Lane wrote:
> "Eric Brown" <bigwhitecow@hotmail.com> writes:
> > [ planning a 9-table query takes too long ]
>
> See http://www.postgresql.org/docs/7.4/static/explicit-joins.html
> for some useful tips.
>
Is this the best answer we've got? For me with an empty table this query
takes 4 seconds to plan, is that the expected planning time? I know I've
got nine table queries that don't take that long.
Setting geqo_threshold less than 9, it takes 1 second to plan. Does this
indicate that geqo_threshold is set too high, or is it a tradeoff between
planning time and plan quality? If the planning time is so high because
the are a large number of possible join orders, should geqo_threhold be
based on the number of possible plans somehow instead of the number of
tables involved?
Kris Jurka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: books@ejurka.com, tgl@sss.pgh.pa.us, bigwhitecow@hotmail.com
Subject: Re: severe performance issue with planner
In-Reply-To: <Pine.BSO.4.56.0403132240261.491@leary.csoft.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox