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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas H(dot)" <me(at)alternize(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join
Date: 2006-11-10 01:24:22
Message-ID: 14219.1163121862@sss.pgh.pa.us
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.

regards, tom lane

Attachment Content-Type Size
joinsize.patch application/octet-stream 6.0 KB

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Broersma Jr 2006-11-10 01:26:39 Re: AutoVacuum on demand?
Previous Message Glen Parker 2006-11-10 01:23:56 Re: AutoVacuum on demand?