From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Bracket, brace, parenthesis |
Date: | 2021-05-27 12:08:46 |
Message-ID: | YK+Lzj55DgrnFqBh@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 27, 2021 at 03:20:10PM +0900, Kyotaro Horiguchi wrote:
> At Fri, 14 May 2021 10:04:57 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in
>> +1. I tend to write "square bracket" or "curly brace" when I want to
>> be extra clear, but I think the bare terms are widely understood to
>> have those meanings.
>
> Thanks! I think the message is new in 14 so we can fix it right
> away. The attached is the version with a commit message added.
No objections from me to fix that on HEAD now for clarity, let's wait
a bit and see if others have more comments. You have missed an update
of multirangetypes.out, by the way.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-05-27 13:34:08 | Re: Move pg_attribute.attcompression to earlier in struct for reduced size? |
Previous Message | Robert Haas | 2021-05-27 11:58:33 | Re: Move pg_attribute.attcompression to earlier in struct for reduced size? |