From: Gregory Stark <stark@enterprisedb.com>
To: "PFC" <lists@peufeu.com>
Cc: <pgsql-performance@postgresql.org>
Subject: Re: PREPARE and stuff
In-Reply-To: <op.tud8ogmscigqcu@apollo13> (lists@peufeu.com's message of "Sat,
	23 Jun 2007 23:30:06 +0200")
Organization: EnterpriseDB
References: <op.tud8ogmscigqcu@apollo13>
Date: Sat, 23 Jun 2007 23:02:25 +0100
Message-ID: <87myyq9vny.fsf@oxford.xeocode.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"PFC" <lists@peufeu.com> writes:

> 	Suppose a web application with persistent database connections.
> 	I have some queries which take longer to plan than to execute !

There have periodically been discussions about a shared plan cache but
generally the feeling is that it would do more harm than good and there are no
plans to implement anything like that.

For a web application though you would expect to be executing the same queries
over and over again since you would be executing the same pages over and over
again. So just a regular prepared query ought to good for your needs.

You do not want to be reconnecting to the database for each page fetch.
Replanning queries is the least of the problems with that approach.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com