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+TgmobVma9x_viC8OYxcm67hVygh7HE5rDgWGQ5YLcW2EX96g@mail.gmail.com
Whole thread Raw
In response to Re: Set search_path + server-prepared statements = cached plan must not change result type  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
List pgsql-hackers
On Mon, Jan 25, 2016 at 2:11 PM, Vladimir Sitnikov
<sitnikov.vladimir@gmail.com> wrote:
> I want to treat 'prepare' operation as an optimization step, so it is functionally equivalent to sending a query
text.
>
> In other words, I would like backend to track search_path and other parameters if necessary transparently‎, creating
(caching)different execution plans if different plans are required. 
> ‎
> Does that make sense?‎

Hmm, so in your example, you actually want replanning to be able to
change the cached plan's result type?

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [POC] FETCH limited by bytes.
Next
From: Robert Haas
Date:
Subject: Re: Combining Aggregates