From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John Naylor <jcnaylor(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: a way forward on bootstrap data |
Date: | 2018-03-22 14:40:48 |
Message-ID: | 32657.1521729648@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
John Naylor <jcnaylor(at)gmail(dot)com> writes:
> On 3/22/18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> While I'm thinking of it --- I noticed one or two places where you
>> had "BKI_DEFAULT(\0)".
> Hmm, I only see this octal in pg_type.h
> char typdelim BKI_DEFAULT(\054);
Sorry, I was going by memory rather than looking at the code.
> Which I hope is fine.
I don't really think it's legal C; I'd rather write BKI_DEFAULT('\054').
> Were you thinking of this comment in
> pg_attribute.h? We use the double-quoted empty string for postgres.bki
> and change it to '\0' for schemapg.h.
> /* One of the ATTRIBUTE_IDENTITY_* constants below, or '\0' */
> char attidentity BKI_DEFAULT("");
That definitely seems like a hack --- why not BKI_DEFAULT('\0') ?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2018-03-22 14:44:21 | Re: pgbench - add \if support |
Previous Message | Alvaro Herrera | 2018-03-22 14:38:27 | Re: WIP: a way forward on bootstrap data |