Re: pg_size_pretty, SHOW, and spaces - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_size_pretty, SHOW, and spaces
Date
Msg-id CA+TgmoabmRseF-G33KhW3YCiWOXK8o2qpvUx7X=0bMyOib0Byw@mail.gmail.com
Whole thread Raw
In response to Re: pg_size_pretty, SHOW, and spaces  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_size_pretty, SHOW, and spaces  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Fri, Aug 5, 2016 at 11:06 AM, Bruce Momjian <bruce@momjian.us> wrote:
> On Fri, Aug  5, 2016 at 10:57:35AM -0400, Peter Eisentraut wrote:
>> On 8/2/16 12:51 PM, Bruce Momjian wrote:
>> > Yes, that's a strong argument for using a space.  I have adjusted the
>> > patch to use spaces in all reasonable places.  Patch attached, which I
>> > have gzipped because it was 133 KB.  (Ah, see what I did there?)  :-)
>> >
>> > I am thinking of leaving the 9.6 docs alone as I have already made them
>> > consistent (no space) with minimal changes.  We can make it consistent
>> > the other way in PG 10.
>>
>> I don't think anyone wanted to *remove* the spaces in the documentation.
>>  I think this change makes the documentation harder to read.
>
> Well, we had spaces in only a few places in the docs, and as I said, it
> is not consistent.  Do you want those few put back for 9.6?

+1 for that.  I can't see how it's good for 10 to be one way, 9.6 to
be the opposite way, and 9.5 and prior to be someplace in the middle.
That seems like a back-patching mess.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: truncate trigger for foreign data wrappers
Next
From: Fujii Masao
Date:
Subject: Re: pg_replication_origin_xact_reset() and its argument variables