Date: Wed, 3 Jun 2020 18:38:14 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
	Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Adding xreflable
Message-ID: <20200603223814.GA7455@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200602160717.GA16329@momjian.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2020-Jun-02, Bruce Momjian wrote:

> I can adjust things, but what logic are we following?  Before my patch,
> sepgsql had an xreflabel, and vacuumlo did not.  I would like to have a
> documented policy of where we should have xreflabels, and where not, and
> I can then adjust things to match.  I don't mind using <link> but it is
> confusing to be able to reference xreflabels in some places and be
> required to use link in others.

I think a possible rationale would be to *not* include xreflabel for
elements that get numbered (so references become, e.g., "see Section 32.5"),
and include them for those that don't -- so that they can be referenced
at all.

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