DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender;
	b=VqH62aA5hEBkoNGXu8TFC4ewJgv8Vuq6rltVJxUVoTx8c4UbmXknoivX27do6F4Zl9NFnHnwRTnHB4NLlACBoP3Dr9tg9WIq106ZJC3+2mrNhUyxeZ0LdTaNM+PSke5w+EMM/8+OQqrvVO99QR5WXUJSdR6xwpj7U/hh4ARM62o=
Message-ID: <467D95C4.4020407@enterprisedb.com>
Date: Sat, 23 Jun 2007 22:51:00 +0100
From: Heikki Linnakangas <heikki@enterprisedb.com>
User-Agent: Icedove 1.5.0.10 (X11/20070329)
MIME-Version: 1.0
To: PFC <lists@peufeu.com>
CC: pgsql-performance@postgresql.org
Subject: Re: PREPARE and stuff
References: <op.tud8ogmscigqcu@apollo13>
In-Reply-To: <op.tud8ogmscigqcu@apollo13>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

PFC wrote:
> 
>     Suppose a web application with persistent database connections.
>     I have some queries which take longer to plan than to execute !
> 
>     I with there was a way to issue a PREPARE (like "PERSISTENT PREPARE").
>     Now all Postgres connections would know that prepared statement foo( 
> $1, $2, $3 ) corresponds to some SQL query, but it wouldn't plan it yet. 
> Just like a SQL function.
>     When invoking EXECUTE foo( 1,2,3 ) on any given connection the 
> statement would get prepared and planned. Then on subsequent invocations 
> I'd just get the previously prepared plan.

How would that be different from the current PREPARE/EXECUTE? Do you 
mean you could PREPARE in one connection, and EXECUTE in another? If 
you're using persistent connections, it wouldn't be any faster than 
doing a PREPARE once in each connection.

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