Horton

Re: Prepared statements fail after schema changes with surprising error

Dimitri Fontaine <dimitri@2ndquadrant.fr>

View thread View on postgr.es
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Stephen Frost <sfrost@snowman.net>, Peter van Hardenberg <pvh@pvh.ca>, Peter Geoghegan <peter.geoghegan86@gmail.com>, "pgsql-hackers\@postgresql.org Hackers" <pgsql-hackers@postgresql.org>
Date: 2013-01-25T08:43:47Z
Lists: pgsql-hackers 
Tom Lane <tgl@sss.pgh.pa.us> writes:
> I wrote:
>> Here's a draft patch for that.  I've not looked yet to see if there's
>> any documentation that ought to be touched.
>
> And now with the documentation.  If I don't hear any objections, I plan
> to commit this tomorrow.

Certainly no objections from me: I had only a cursory look at it, enough
to agree with the documented behaviour changes. I think it will also
make it safer to use prepared statements in pooling environments.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support