Re: Avoiding bad prepared-statement plans. - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Avoiding bad prepared-statement plans.
Date
Msg-id 871vgir361.fsf@hi-media-techno.com
Whole thread Raw
In response to Re: Avoiding bad prepared-statement plans.  ("Pierre C" <lists@peufeu.com>)
Responses Re: Avoiding bad prepared-statement plans.
List 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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: A thought: should we run pgindent now?
Next
From: "Marc G. Fournier"
Date:
Subject: SR: "pseudo replication database of the primary" ...