| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Use %u to print user mapping's umid and userid |
| Date: | 2016-05-12 18:35:28 |
| Message-ID: | CA+TgmoZR6j4pEEf92gionBjgM5N7zGJ8WcF3_kRhqy6ZNKGjXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 12, 2016 at 2:29 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Robert Haas wrote:
>> My suggestion is that we switch from using a List to marshal the data
>> to using an ExtensibleNode. An advantage of that is that we'd have
>> some in-core test coverage for the ExtensibleNode stuff. In theory it
>> ought to be simpler and less messy, too, but I guess we'll find out.
>
> So the data in the list has a certain specific meaning according to its
> position within the list? And the enum being modified by this patch,
> corresponds to knowledge of what each element in the list is?
Right.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-12 18:43:24 | Re: alter table alter column ... (larger type) ... when there are dependent views |
| Previous Message | Alvaro Herrera | 2016-05-12 18:29:48 | Re: Use %u to print user mapping's umid and userid |