Re: Prepared statements fail after schema changes with surprising error

Andres Freund <andres@2ndquadrant.com>

From: Andres Freund <andres@2ndquadrant.com>
To: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter van Hardenberg <pvh@pvh.ca>, Peter Geoghegan <peter.geoghegan86@gmail.com>, "pgsql-hackers@postgresql.org Hackers" <pgsql-hackers@postgresql.org>
Date: 2013-01-22T13:32:51Z
Lists: pgsql-hackers
On 2013-01-22 14:24:26 +0100, Dimitri Fontaine wrote:
> 
> Tom Lane <tgl@sss.pgh.pa.us> writes:
> >> DROP SCHEMA public;
> >> CREATE SCHEMA public;
> >
> > changes the OID of schema public, whereas the search_path that's cached
> > for the cached plan is cached in terms of OIDs.  So while there is a
> > table named public.z1 at the end of the sequence, it's not in any schema
> > found in the cached search path.
> 
> The DROP SCHEMA should invalidate the cached plan, certainly?

Afaics the error happens during replanning of the invalidated plan.

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services