Horton
Menu

Re: Avoiding bad prepared-statement plans.

Dimitri Fontaine <dfontaine@hi-media.com>

View thread
From: Dimitri Fontaine <dfontaine@hi-media.com>
To: "Pierre C" <lists@peufeu.com>
Cc: "Greg Stark" <gsstark@mit.edu>, "Jeroen Vermeulen" <jtv@xs4all.nl>, "Tom Lane" <tgl@sss.pgh.pa.us>, "Robert Haas" <robertmhaas@gmail.com>, "Bart Samwel" <bart@samwel.tk>, "Pavel Stehule" <pavel.stehule@gmail.com>, pgsql-hackers@postgresql.org
Date: 2010-02-18T15:09:42Z
Lists: pgsql-hackers 
"Pierre C" <lists@peufeu.com> writes:
> Problem with prepared statements is they're a chore to use in web apps,
> especially PHP, since after grabbing a connection from the pool, you don't
> know if it has prepared plans in it or not.

Have you met preprepare yet?

  http://preprepare.projects.postgresql.org/README.html
  http://packages.debian.org/source/sid/preprepare

Regards,
-- 
dim