Re: [HACKERS] Re: [COMMITTERS] pgsql: Invent a "one-shot" variant of CachedPlans for better performanc

2013-01-06 Thread Simon Riggs
On 5 January 2013 19:15, Tom Lane wrote: >> 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. > >

Re: [HACKERS] Re: [COMMITTERS] pgsql: Invent a "one-shot" variant of CachedPlans for better performanc

2013-01-05 Thread Tom Lane
Simon Riggs writes: > On 4 January 2013 22:42, Tom Lane wrote: >> Invent a "one-shot" variant of CachedPlans for better performance. > 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 variet

[HACKERS] Re: [COMMITTERS] pgsql: Invent a "one-shot" variant of CachedPlans for better performanc

2013-01-04 Thread Simon Riggs
On 4 January 2013 22:42, Tom Lane 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.) > > H