Re: Set search_path + server-prepared statements = cached plan must not change result type

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Set search_path + server-prepared statements = cached plan must not change result type
Date: 2016-01-25 17:39:29
Message-ID: CA+TgmoYhpQxeo3oDwzvjKnZsdneKNEGb6vEN3Vv-Dy3ZzGeyAg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 21, 2016 at 3:55 PM, Vladimir Sitnikov
<sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
> Robert>Are you really seeing the same behavior in all versions?
>
> I do not have "pre 9.1" at hand, however all 9.1, 9.2, 9.3, 9.4, and
> 9.5 are affected.
>
> 9.1 just silently executes "old statement" as if search_path was not
> modified at all.
> 9.2, 9.3, 9.4, and 9.5 all fail with "cached plan must not change
> result type" error.

What is the ideal behavior, in your view?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-01-25 17:43:53 Re: is there a deep unyielding reason to limit U&'' literals to ASCII?
Previous Message Robert Haas 2016-01-25 17:13:54 Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)