Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join

From: "Thomas H(dot)" <me(at)alternize(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>, "Magnus Hagander" <mha(at)sollentuna(dot)net>
Subject: Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join
Date: 2006-11-10 02:09:03
Message-ID: 0d5701c7046d$38c35420$0201a8c0@iwing
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>I wrote:
>> This didn't matter a whole lot back when the planner couldn't reorder
>> outer joins, but now that it can, it's more important that the estimates
>> be accurate.
>
>> I'm not sure if this is feasible to fix before 8.2, but I'll take a
>> look.
>
> Actually, the changes were far more localized than I first feared.
> Please apply the attached patch to your copy and see what you get for
> your problem query.

thanks for the quick patch. unfortunately i'm stuck with the win32 version
for now and haven't got the possibility to compile from source (yet)...

maybe magnus can provide me a custom win32 executable of b3 that contains
this patch [and the one for the xlog lockup]?

best wishes,
thomas

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Cornelia Boenigk 2006-11-10 02:13:35 Re: zero values in statistic views
Previous Message Matthew Peter 2006-11-10 02:06:00 Re: RULE - special variables?