Subject: Re: Retaining execution plans between connections?
From: Neil Conway <neilc@samurai.com>
To: James Russell <internationalhobo@gmail.com>
Cc: pgsql-performance@postgresql.org
In-Reply-To: <3a3a16930601200114p27ccb3fdn750286898f39c405@mail.gmail.com>
References: <3a3a16930601200114p27ccb3fdn750286898f39c405@mail.gmail.com>
Content-Type: text/plain
Date: Fri, 20 Jan 2006 10:14:59 -0500
Message-Id: <1137770099.9330.12.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2006-01-20 at 18:14 +0900, James Russell wrote:
> I am looking to speed up performance, and since each page executes a
> static set of queries where only the parameters change, I was hoping
> to take advantage of stored procedures since I read that PostgreSQL's
> caches the execution plans used inside stored procedures.

Note that you can also take advantage of plan caching by using prepared
statements (PREPARE, EXECUTE and DEALLOCATE). These are also session
local, however (i.e. you can't share prepared statements between
connections).

> As I said, I can't share the DB connection between pages (unless
> someone knows of a way to do this and still retain a level of
> separation between pages that use the same DB connection).

You can't share plans among different sessions at the moment. Can you
elaborate on why you can't use persistent or pooled database
connections?

-Neil