Re: Persistent Plan Cache - Mailing list pgsql-performance

From Heikki Linnakangas
Subject Re: Persistent Plan Cache
Date
Msg-id 4AADCE10.4070306@enterprisedb.com
Whole thread Raw
In response to Re: Persistent Plan Cache  (Joshua Rubin <jrubin@esoft.com>)
Responses Re: Persistent Plan Cache  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-performance
Joshua Rubin wrote:
> We "hardcode" the parts of the where clause so that the prepared plan
> will not vary among the possible partitions of the table. The only
> values that are bound would not affect the planner's choice of table.

Then you would benefit from using prepared statements in the client,
and/or connection pooling to avoid having to re-prepare because of
reconnecting.

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

pgsql-performance by date:

Previous
From: Joshua Rubin
Date:
Subject: Re: Persistent Plan Cache
Next
From: zz_11@mail.bg
Date:
Subject: Re: possible wrong query plan on pg 8.3.5,