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

From Bruce Momjian
Subject Re: pg_size_pretty, SHOW, and spaces
Date
Msg-id 20160805150615.GC5068@momjian.us
Whole thread Raw
In response to Re: pg_size_pretty, SHOW, and spaces  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: pg_size_pretty, SHOW, and spaces  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
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?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+                     Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Next
From: Peter Eisentraut
Date:
Subject: Re: handling unconvertible error messages