DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=PKo+mHF7JuIpnBfzq+x4KMaICYvvkWvaRLA/BQLGwuRAtqy1R2AovlfNioAwltOZId
	S03Pl3NMcrTmRnqwNxObTRBSGnyKm/rLQClmiDkyuRvBSxmMhDvqDSwkoomBWjagdDUY
	hH+4aGDrijl4U288JN/tCOeUP3uSEZ/P+3lKo=
Message-ID: <33b743250812310711r6fb8fb1ydb72aee090d7bc06@mail.gmail.com>
Date: Wed, 31 Dec 2008 07:11:17 -0800
From: bricklen <bricklen@gmail.com>
To: "Guillaume Smet" <guillaume.smet@gmail.com>
Subject: Re: Poor plan choice in prepared statement
Cc: pgsql-performance@postgresql.org
In-Reply-To: <1d4e0c10812310112h2e96001ap86a42e78803a18bc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <33b743250812301059u31ce82faw3d72a38280b37402@mail.gmail.com>
	<1d4e0c10812310112h2e96001ap86a42e78803a18bc@mail.gmail.com>

Hi Guillaume,

On Wed, Dec 31, 2008 at 1:12 AM, Guillaume Smet
<guillaume.smet@gmail.com> wrote:
> On Tue, Dec 30, 2008 at 7:59 PM, bricklen <bricklen@gmail.com> wrote:
>> I would like to continue to use bind variables to prevent sql
>> injection, but I'd like to force a plan re-parse for every single
>> query (if necessary?)
>
> As far as I understand your problem, you don't care about using
> prepared statements.
>
> If so, you can:
> - either use pg_query_params():
> http://www.php.net/manual/en/function.pg-query-params.php
> - or use an unnamed prepared statements when you don't want a prepared
> statement if, for some reason, you really need to use prepared
> statements in a few cases: you can specify an empty string as plan
> name. The condition for this one is that you need to upgrade to a
> recent version of 8.3 as postponed planning of unnamed prepared
> statements is a new feature of 8.3 and was broken in 8.3.0 and 8.3.1.
>
> --
> Guillaume
>

I will look into the pg_query_params() function to see if it works for
us. I don't think your second suggestion is going to work for us,
since we are stuck on 8.2 for the foreseeable future.

Thanks for the tips though, I appreciate it!

Bricklen