Postgres Pro
Downloads
Home   >   mailing lists

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

From Vladimir Sitnikov
Subject Re: Set search_path + server-prepared statements = cached plan must not change result type
Date
Msg-id 20160125191149.28913750.3635.8248@gmail.com
Whole thread Raw
In response to Re: Set search_path + server-prepared statements = cached plan must not change result type  (Tom Lane <tgl@sss.pgh.pa.us>)
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  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
Tree view 
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?‎
‎
Vladimir‎

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Patch: ResourceOwner optimization for tables with many partitions
Next
From: Craig Ringer
Date:
Subject: Re: WIP: Failover Slots