Re: Pre-alloc ListCell's optimization
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-05-26T16:38:15Z
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 →
-
Replace the parser's namespace tree (which formerly had the same
- a4996a895399 8.1.0 cited
-
Turns out that my recent elimination of the 'redundant' flatten_andors()
- 56c88772911b 8.1.0 cited
Excerpts from Stephen Frost's message of mar may 24 22:56:21 -0400 2011: > Greetings, > > Someone (*cough*Haas*cough) made a claim over beers at PGCon that it > would be very difficult to come up with a way to pre-allocate List > entries and maintain the current List API. I'll admit that it wasn't > quite as trivial as I had *hoped*, but attached is a proof-of-concept > patch which does it. I think what this patch is mainly missing is a description of how the new allocation is supposed to work, so that we can discuss the details without having to reverse-engineer them from the code. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support