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

Re: Prepared statements considered harmful

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prepared statements considered harmful
Date: 2006-08-31 16:19:02
Message-ID: 20060831161902.GE27851@svana.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Aug 31, 2006 at 11:27:18AM -0400, Tom Lane wrote:
> > I'd wish that we reconsider when and how prepared statements are used.  The 
> > JDBC interface and PL/pgSQL are frequently noticed perpetrators, but the 
> > problem is really all over the place.
> 
> AFAIK those are the only two places where preparation is the default
> ... what else were you thinking of?

Perl DBI (DBD::Pg) defaults to prepared plans when connecting to a
version 8.0 or higher server.

Or at least, that's the way I read the documentation.

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog(at)svana(dot)org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

pgsql-hackers by date

Next:From: Chris BrowneDate: 2006-08-31 16:26:44
Subject: Re: [COMMITTERS] pgsql: Second try committing the path changes.
Previous:From: AgentMDate: 2006-08-31 16:17:47
Subject: Re: Prepared statements considered harmful

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