To: Oliver Crosby <ryusei@gmail.com>
Cc: "Joshua D. Drake" <jd@commandprompt.com>, pgsql-performance@postgresql.org
Subject: Re: Looking for tips 
In-reply-to: <1efd553a05071912111f6a3121@mail.gmail.com> 
References: <1efd553a05071910427b290203@mail.gmail.com>
	<42DD3D55.9020508@commandprompt.com>
	<1efd553a050719112126b8d981@mail.gmail.com>
	<8446.1121799660@sss.pgh.pa.us>
	<1efd553a05071912111f6a3121@mail.gmail.com>
Comments: In-reply-to Oliver Crosby <ryusei@gmail.com>
	message dated "Tue, 19 Jul 2005 15:11:15 -0400"
Date: Tue, 19 Jul 2005 15:16:31 -0400
Message-ID: <8613.1121800591@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Oliver Crosby <ryusei@gmail.com> writes:
>> You could possibly get some improvement if you can re-use prepared plans
>> for the queries; but this will require some fooling with the client code
>> (I'm not sure if DBD::Pg even has support for it at all).

> Aye. We have prepared statements.

Ah, but are they really prepared, or is DBD::Pg faking it by inserting
parameter values into the query text and then sending the assembled
string as a fresh query?  It wasn't until about 7.4 that we had adequate
backend support to let client libraries support prepared queries
properly, and I'm unsure that DBD::Pg has been updated to take advantage
of that support.

			regards, tom lane