From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: ArrayLists instead of List (for some things) |
Date: | 2017-11-02 14:24:51 |
Message-ID: | CAMsr+YHf9i7HUT6Fd4CeVjQZezNSE9kaNNU3yjx8t9FSntspPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2 November 2017 at 22:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
>> Comments on the design are welcome, but I was too late to the
>> commitfest, so there are other priorities. However, if you have a
>> strong opinion, feel free to voice it.
>
> I do not like replacing Lists piecemeal; that's a recipe for ongoing
> API breakage and back-patching pain. Plus we'll then have *four*
> different linked-list implementations in the backend, which sure
> seems like too many.
>
> We've jacked up the List API and driven a new implementation underneath
> once before. Maybe it's time to do that again.
I know some systems use hybrid linked array-lists, where linked list
cells are multi-element.
https://en.wikipedia.org/wiki/Unrolled_linked_list
I don't have much experience with them myself.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2017-11-02 14:26:39 | Re: ArrayLists instead of List (for some things) |
Previous Message | David Rowley | 2017-11-02 14:22:28 | Re: ArrayLists instead of List (for some things) |