From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peterson, Bjorn <Bjorn.Peterson@pearson.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: enable_XXX options
Date: Fri, 01 Apr 2005 11:36:43 -0500
Message-ID: <7068.1112373403@sss.pgh.pa.us> (raw)
In-Reply-To: <42E7C401A4CBCD49829BB53DDD538BA40211439B@chmpgexgmail3.ic.ncs.com>
References: <42E7C401A4CBCD49829BB53DDD538BA40211439B@chmpgexgmail3.ic.ncs.com>
"Peterson, Bjorn" <Bjorn.Peterson@pearson.com> writes:
> I have a query in my application that takes an unreasonable amount of time
> to complete (>4.5 hours execution time). After reviewing the EXPLAIN and
> EXPLAIN ANALYZE output for that and similar queries, my colleagues and I
> determined that turning off the enable_nestloop option might help - we
> noticed dramatic speed improvements for that specific query after doing so
> (<2 minutes execution time). I was warned not to mess with the enable_XXX
> options in a production environment, but does anyone see any problem with
> turning off the enable_nestloop option right before executing my query and
> turning it back on afterwards?
That's what it's there for ... but it would be useful to look into why
the planner gets it so wrong without that hint. Could we see EXPLAIN
ANALYZE both ways?
regards, tom lane
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: tgl@sss.pgh.pa.us, Bjorn.Peterson@pearson.com
Subject: Re: enable_XXX options
In-Reply-To: <7068.1112373403@sss.pgh.pa.us>
* 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