| From: | John Naylor <jcnaylor(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: a way forward on bootstrap data |
| Date: | 2018-03-22 15:11:33 |
| Message-ID: | CAJVSVGX-khG6mjbdpKSgkyfPvCn+y-EF=NCrxAB0G32OHM+z=w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/22/18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I don't really think it's legal C; I'd rather write BKI_DEFAULT('\054').
Okay, I'll do that.
>> 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') ?
Hmm, yes, the way I had it, the comment is a mystery. I'll switch it around.
-John Naylor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2018-03-22 15:23:44 | Re: WIP: Covering + unique indexes. |
| Previous Message | Robert Haas | 2018-03-22 15:07:48 | Re: faster testing with symlink installs |