Re: Problem with index not being chosen inside PL/PgSQL function... - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Problem with index not being chosen inside PL/PgSQL function...
Date
Msg-id dcc563d10712181002j543165ddk75e967ff87d23875@mail.gmail.com
Whole thread Raw
In response to Re: Problem with index not being chosen inside PL/PgSQL function...  ("Weber, Geoffrey M." <Geoffrey.Weber@mcleodusa.com>)
Responses Re: Problem with index not being chosen inside PL/PgSQL function...
List pgsql-general
On Dec 18, 2007 10:54 AM, Weber, Geoffrey M.
<Geoffrey.Weber@mcleodusa.com> wrote:
> Tom,
>
> Yes, the distribution must be what's doing it.  I guess I knew that subconciously, but was looking for something like
hintsto force the planner to do what I wanted.  Instead it looks like I'll have to do a bit of tweaking with my
indexes. Probably a partial index on the 'not_displayed_id' column.  It'll be very small and shouldn't cause much
overhead. I was trying to keep my index count down, and have had a dual-column index on (replaced_by_id,
not_displayed_id)to this point. 

Fix not with a hammer that which you can fix with a screwdriver.  Fix
not with a screwdriver that which you can fix with a knob

Have you tried increasing the stats target of the guilty column and
reanalyzing to see if that helps?

pgsql-general by date:

Previous
From: Nathan Wilhelmi
Date:
Subject: Specify client encoding for backups...
Next
From: Benoît Carpentier
Date:
Subject: free ETL tool using postgreSQL, new major release