Date: Thu, 26 Sep 2019 17:17:55 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Most-common value docs in PG 12
Message-ID: <20190926201755.GA18930@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20190926200522.GB16366@momjian.us>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

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:

> > >       <para>
> > >        The name of a table column to be covered by the computed statistics.
> > > -      At least two column names must be given.
> > > +      At least two column names must be given;  the order of the column names
> > > +      is insignificant.
> > >       </para>

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services