Re: Caching for stable expressions with constant arguments v6
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Marti Raudsepp <marti@juffo.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Jaime Casanova <jaime@2ndquadrant.com>
Date: 2012-08-27T13:50:22Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Refactor simplify_function et al to centralize argument simplification.
- 81a646febe87 9.2.0 cited
Where are we on this? --------------------------------------------------------------------------- On Mon, Jan 16, 2012 at 07:06:45PM +0200, Marti Raudsepp wrote: > Hi list, > > Here's v6 of my expression caching patch. The only change in v6 is > added expression cost estimation in costsize.c. I'm setting per-tuple > cost of CacheExpr to 0 and moving sub-expression tuple costs into the > startup cost. > > As always, this work is also available from my Github "cache" branch: > https://github.com/intgr/postgres/commits/cache > > This patch was marked as "Returned with Feedback" from the 2011-11 > commitfest. I expected to get to tweak the patch in response to > feedback before posting to the next commitfest. But said feedback > didn't arrive, and with me being on vacation, I missed the 2012-01 CF > deadline. :( > > I will add it to the 2012-01 commitfest now, I hope that's OK. If not, > feel free to remove it and I'll put it in 2012-Next. > > PS: Jaime, have you had a chance to look at the patch? Even if you're > not done with the review, I'd be glad to get some comments earlier. > And thanks for reviewing. > > Regards, > Marti > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +