Skip site navigation (1) Skip section navigation (2)

Re: Avoiding bad prepared-statement plans.

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: "Pierre C" <lists(at)peufeu(dot)com>
Cc: "Greg Stark" <gsstark(at)mit(dot)edu>, "Jeroen Vermeulen" <jtv(at)xs4all(dot)nl>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Bart Samwel" <bart(at)samwel(dot)tk>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Avoiding bad prepared-statement plans.
Date: 2010-02-18 15:09:42
Message-ID: 871vgir361.fsf@hi-media-techno.com (view raw or flat)
Thread:
Lists: pgsql-hackers
"Pierre C" <lists(at)peufeu(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-02-18 15:11:29
Subject: Re: A thought: should we run pgindent now?
Previous:From: Pierre CDate: 2010-02-18 14:58:25
Subject: Re: Avoiding bad prepared-statement plans.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group