Date: Thu, 26 Sep 2019 16:20:59 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Most-common value docs in PG 12
Message-ID: <20190926202059.GD16366@momjian.us>
References: <20190926200522.GB16366@momjian.us>
 <20190926201755.GA18930@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190926201755.GA18930@alvherre.pgsql>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Thu, Sep 26, 2019 at 05:17:55PM -0300, Alvaro Herrera wrote:
> On 2019-Sep-26, Bruce Momjian wrote:
> 
> > On Wed, Sep 11, 2019 at 06:15:22PM -0300, Alvaro Herrera wrote:
> > > On 2019-Aug-30, Bruce Momjian wrote:
> > > 
> > > > OK, how is this patch?  I didn't mention psql since I think everyone
> > > > expects psql to show all information about tables and indexes.
> > > 
> > > Why would you change perform.sgml?  It seems unnecessary; the commands
> > > shown work fine.
> > 
> > I realize they work fine, but the ordering in the examples not matching
> > the defined order suggests that ordering matters, but it does not.
> 
> Well, I mean exactly the other way around: the fact that the orders
> don't match illustrates that the order is not important.  And that is
> reinforced by the explanation indicating explicitly that it does not
> matter:

Uh, people normally list things in defined order, so you would usually
not list them in non-defined order unless there is a purpose.  Doing
that just to illustrate the order doesn't matter seems odd.

-- 
  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 +