From: Tom Lane <tgl@sss.pgh.pa.us>
To: Doug Eck <deck1@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Identical DB's, different execution plans
Date: Mon, 29 Sep 2008 12:42:01 -0400
Message-ID: <15191.1222706521@sss.pgh.pa.us> (raw)
In-Reply-To: <926018.53635.qm@web45204.mail.sp1.yahoo.com>
References: <926018.53635.qm@web45204.mail.sp1.yahoo.com>
Doug Eck <deck1@yahoo.com> writes:
> Any ideas as to what could the first db to opt for the slower subquery rather than the merge?
Not from the information given. Presumably db1 thinks that the
mergejoin plan would be slower, but why it thinks that isn't clear yet.
Try setting enable_nestloop = off (and enable_hashjoin = off if it then
wants a hashjoin) and then post the EXPLAIN ANALYZE results.
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, deck1@yahoo.com
Subject: Re: Identical DB's, different execution plans
In-Reply-To: <15191.1222706521@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