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

From Robert Haas
Subject Re: Set search_path + server-prepared statements = cached plan must not change result type
Date
Msg-id CA+TgmoZ77PPtJbQ7BcXZHT2qnQcPxFExAC4Ba1qpxHApa=B4OQ@mail.gmail.com
Whole thread Raw
In response to Re: Set search_path + server-prepared statements = cached plan must not change result type  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Jan 25, 2016 at 12:47 PM, Andres Freund <andres@anarazel.de> wrote:
> On 2016-01-25 12:39:29 -0500, Robert Haas wrote:
>> What is the ideal behavior, in your view?
>
> FWIW, I think that for a lot of practical cases the previous behaviour,
> where a prepared statement was defined in the context of the search path
> set during the PREPARE, made a lot more sense.  The current behaviour
> makes a few corner cases (dropped, or relations moved between schemas)
> simpler, while making real world things harder (different parts of an
> application using different search paths, drivers, increase in planning
> time).

That's a defensible position, but Vladimir didn't seem to like
*either* behavior.

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Set search_path + server-prepared statements = cached plan must not change result type
Next
From: Tom Lane
Date:
Subject: Re: is there a deep unyielding reason to limit U&'' literals to ASCII?