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

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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 19:11:49
Message-ID: 20160125191149.28913750.3635.8248@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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‎

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-01-25 19:34:31 Re: WIP: Failover Slots
Previous Message Aleksander Alekseev 2016-01-25 18:58:20 Re: Patch: ResourceOwner optimization for tables with many partitions