From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH 04/16] Add embedded list interface (header only) |
Date: | 2012-06-20 13:24:58 |
Message-ID: | CA+TgmoYcjb09xELoQ_NuNmkwnGxh7-aJaRrMJ+0K0EzX7RH9jQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 20, 2012 at 9:12 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Uh. I don't want to just go around and replace anything randomly. Actually I
> don't want to change anything for now except whats necessary to get the patch
> in. The point I tried to make was just that the relatively widespread usage of
> similar structure make it likely that it can be used in more places in future.
Well, the question is for anywhere you might be thinking of using
this: why not just use List? We do that in a lot of other places, and
there's not much reason to event something new unless there is a
problem with what we already have. I assume this is related to
logical replication somehow, but it's not clear to me exactly what
problem you hit doing this in the obvious way.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2012-06-20 13:25:36 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
Previous Message | Ryan Kelly | 2012-06-20 13:23:38 | [PATCH] Add some more documentation for array indexes/operators |