Re: Postgres optimizer choosing wrong index - Mailing list pgsql-general

From Jack Orenstein
Subject Re: Postgres optimizer choosing wrong index
Date
Msg-id 49072350.3040505@hds.com
Whole thread Raw
In response to Re: Postgres optimizer choosing wrong index  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:
> Jack Orenstein <jack.orenstein@hds.com> writes:
>> EXPLAIN says that the correct index is being used -- it didn't used
>> to. However, pg_stat* says otherwise. In my test, I have exactly one
>> dh value. Running EXPLAIN with this value produces a plan using idx_dh
>> (the correct index), but pg_stats says that idx_dn is being used (see
>> psql session below).
>
> Yeah, if you are using cached plans (via PREPARE or plpgsql functions)
> then the plan stays the same for the life of the session ... pre 8.3
> that is.

Thank you.

One of the great things about postgres is being able to understand things all
the way down with the patient help of the actual developers.

Jack

pgsql-general by date:

Previous
From: Allan Kamau
Date:
Subject: Re: Piping CSV data to psql when executing COPY .. FROM STDIN
Next
From: Tom Lane
Date:
Subject: Re: getting our bearings on "out of memory. failed on request of size..."