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

From Tom Lane
Subject Re: Postgres optimizer choosing wrong index
Date
Msg-id 26231.1225147641@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres optimizer choosing wrong index  (Jack Orenstein <jack.orenstein@hds.com>)
Responses Re: Postgres optimizer choosing wrong index  (Jack Orenstein <jack.orenstein@hds.com>)
List pgsql-general
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.

            regards, tom lane

pgsql-general by date:

Previous
From: Mark Cave-Ayland
Date:
Subject: Re: PostgreSQL 8.3.3 chooses wrong query plan when LIMIT 1 added?
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL 8.3.3 chooses wrong query plan when LIMIT 1 added?