Re: Persistent Plan Cache

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Joshua Rubin <jrubin(at)esoft(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Persistent Plan Cache
Date: 2009-09-14 05:01:04
Message-ID: 4AADCE10.4070306@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message zz_11 2009-09-14 06:16:32 Re: possible wrong query plan on pg 8.3.5,
Previous Message Tom Lane 2009-09-13 22:37:00 Re: [PERFORMANCE] work_mem vs temp files issue