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

From Andres Freund
Subject Re: Set search_path + server-prepared statements = cached plan must not change result type
Date
Msg-id 20160125174729.GC25778@awork2.anarazel.de
Whole thread Raw
In response to Re: Set search_path + server-prepared statements = cached plan must not change result type  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Set search_path + server-prepared statements = cached plan must not change result type  (Robert Haas <robertmhaas@gmail.com>)
Re: Set search_path + server-prepared statements = cached plan must not change result type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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).

Andres



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch: ResourceOwner optimization for tables with many partitions
Next
From: Robert Haas
Date:
Subject: Re: Set search_path + server-prepared statements = cached plan must not change result type