Re: planer chooses very bad plan - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: planer chooses very bad plan
Date
Msg-id o2jdcc563d11004111418pca3ad67dyda7e74d5252fd1c1@mail.gmail.com
Whole thread Raw
In response to planer chooses very bad plan  (Corin <wakathane@gmail.com>)
Responses Re: planer chooses very bad plan  (Corin <wakathane@gmail.com>)
List pgsql-performance
On Sun, Apr 11, 2010 at 3:12 PM, Corin <wakathane@gmail.com> wrote:
> Hi,
>
> I'm having a query where the planer chooses a very bad plan.

In both instances your number of rows estimated is WAY higher than the
actual number of rows returned.  Perhaps if you increased
default_statistics_target to 100, 200, 500 etc. re-analyzed, and then
reun explain analyze again.

Also increasing work_mem might encourage the bitmap index scans to occur.

pgsql-performance by date:

Previous
From: Corin
Date:
Subject: planer chooses very bad plan
Next
From: Luke Lonergan
Date:
Subject: Re: planer chooses very bad plan