Re: Followup - expression (functional) index use in joins

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Roger Ging <rging(at)paccomsys(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Followup - expression (functional) index use in joins
Date: 2003-11-27 00:09:25
Message-ID: 18733.1069891765@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Roger Ging <rging(at)paccomsys(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-11-27 00:51:14 Re: For full text indexing, which is better, tsearch2 or
Previous Message LIANHE SHAO 2003-11-26 22:46:24 Re: very large db performance question