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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, 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:47:29
Message-ID: 20160125174729.GC25778@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-01-25 17:49:19 Re: Set search_path + server-prepared statements = cached plan must not change result type
Previous Message Tom Lane 2016-01-25 17:44:45 Re: Patch: ResourceOwner optimization for tables with many partitions