| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter van Hardenberg <pvh(at)pvh(dot)ca>, Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Prepared statements fail after schema changes with surprising error |
| Date: | 2013-01-22 13:32:51 |
| Message-ID: | 20130122133251.GA7590@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-01-22 14:24:26 +0100, Dimitri Fontaine wrote:
>
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-01-22 13:33:15 | Re: Teaching pg_receivexlog to follow timeline switches |
| Previous Message | Dimitri Fontaine | 2013-01-22 13:28:54 | Re: Event Triggers: adding information |