Horton

Re: Pre-alloc ListCell's optimization

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers@postgresql.org
Date: 2011-05-26T17:55:53Z
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 →

  1. Replace the parser's namespace tree (which formerly had the same

  2. Turns out that my recent elimination of the 'redundant' flatten_andors()

On Tue, May 24, 2011 at 10:56 PM, Stephen Frost <sfrost@snowman.net> wrote:
>  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.
>
> [ various points ]

So I guess the first question here is - does it improve performance?

Because if it does, then it's worth pursuing ... if not, that's the
first thing to fix.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company