On 4 January 2013 22:42, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Invent a "one-shot" variant of CachedPlans for better performance.
> Back-patch to 9.2, since this was a performance regression compared to 9.1.
> (In 9.2, place the added struct fields so as to avoid changing the offsets
> of existing fields.)
> Heikki Linnakangas and Tom Lane
Just a moment of reflection here but I did already invent a "one-shot"
plan concept in a patch submission to 9.2, called exactly that, which
enables a variety of optimizations, this being one.
It's a shame that my patch was deferred in favour of your approach,
yet it never happened until now, well after release. Given that I
raised this before the first CF of 9.2, that is not good.
We need a full "one-shot" concept linking the planner and executor for
all sorts of reasons, not just this one. We can discuss the
practicality of individual optimizations but the linkage should be
clear throughout the whole infrastructure.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: Amit kapila||Date: 2013-01-05 04:58:07|
|Subject: Re: Proposal for Allow postgresql.conf values to be
changed via SQL [review]|
|Previous:||From: Josh Berkus||Date: 2013-01-04 23:04:07|
|Subject: Re: dynamic SQL - possible performance regression in 9.2|
pgsql-committers by date
|Next:||From: Peter Eisentraut||Date: 2013-01-05 13:26:06|
|Subject: pgsql: Make some spelling more consistent|
|Previous:||From: Tom Lane||Date: 2013-01-04 22:42:42|
|Subject: pgsql: Invent a "one-shot" variant of CachedPlans for betterperformanc|