Re: RFC: list API / memory allocations

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFC: list API / memory allocations
Date: 2011-11-19 17:33:19
Message-ID: 20111119173319.GA24234@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Now, if you could do something that *doesn't* restrict what operations
> could be applied to the lists, that would be good.

If the API is followed, I believe my previous patch works for
everything, but it wasn't variable about the size of the new list.
Perhaps we could combine the two approaches, though there would be more
overhead from dealing with a variable bitmap for what's currently used.

> I've wished for a long while that we could allocate the list header and
> the first list cell in a single palloc cycle.

You've mentioned that before and, to be honest, I could have sworn that
we're doing that already..

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-11-19 17:35:17 Re: EXPLAIN (plan off, rewrite off) for benchmarking
Previous Message Stephen Frost 2011-11-19 17:31:09 Re: RFC: list API / memory allocations