From: Tom Lane <tgl@sss.pgh.pa.us>
To: Roger Ging <rging@paccomsys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Followup - expression (functional) index use in joins
Date: Wed, 26 Nov 2003 19:09:25 -0500
Message-ID: <18733.1069891765@sss.pgh.pa.us> (raw)
In-Reply-To: <3FC51B2C.2030700@paccomsys.com>
References: <3FC4F360.2090609@paccomsys.com>
<200311261912.01286.dev@archonet.com>
<3FC51B2C.2030700@paccomsys.com>
Roger Ging <rging@paccomsys.com> writes:
> Ran vacuum analyse on both program and logfile tables. Estimates are
> more in line with reality now,
And they are what now? You really can't expect to get useful help here
when you're being so miserly with the details ...
FWIW, I suspect you could force 7.4 to generate 7.3's plan by setting
enable_mergejoin to off (might have to also set enable_hashjoin to off,
if it then tries for a hash join). 7.3 could not even consider those
join types in this example, while 7.4 can. The interesting question
from my perspective is why the planner is guessing wrong about the
relative costs of the plans. EXPLAIN ANALYZE results with each type of
join forced would be useful to look at.
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, rging@paccomsys.com
Subject: Re: Followup - expression (functional) index use in joins
In-Reply-To: <18733.1069891765@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