| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pre-alloc ListCell's optimization |
| Date: | 2011-05-26 17:55:53 |
| Message-ID: | BANLkTimLq8e7F_BFYf7yokkqqeNt2VLWbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 24, 2011 at 10:56 PM, Stephen Frost <sfrost(at)snowman(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | panam | 2011-05-26 18:04:35 | Re: Hash Anti Join performance degradation |
| Previous Message | Robert Haas | 2011-05-26 17:50:45 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |