Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1jjVqZ-0003tD-8Y
	for pgsql-docs@arkaria.postgresql.org; Thu, 11 Jun 2020 22:38:55 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1jjVqY-0000lE-52
	for pgsql-docs@arkaria.postgresql.org; Thu, 11 Jun 2020 22:38:54 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1jjVqX-0000l7-W0
	for pgsql-docs@lists.postgresql.org; Thu, 11 Jun 2020 22:38:53 +0000
Received: from momjian.us ([72.94.173.45])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1jjVqR-0000Oc-CA
	for pgsql-docs@postgresql.org; Thu, 11 Jun 2020 22:38:53 +0000
Received: from bruce by momjian.us with local (Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1jjVqP-0006cz-BW; Thu, 11 Jun 2020 18:38:45 -0400
Date: Thu, 11 Jun 2020 18:38:45 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Adding xreflable
Message-ID: <20200611223845.GB2507@momjian.us>
References: <19807.1589551746@sss.pgh.pa.us>
 <20200515142204.GE3894@momjian.us>
 <22323.1589555218@sss.pgh.pa.us>
 <20200515153034.GG3894@momjian.us>
 <20200515164747.GH3894@momjian.us>
 <8315c0ca-7758-8823-fcb6-f37f9413e6b6@2ndquadrant.com>
 <20200522164518.GG30409@momjian.us>
 <28ff383a-59c1-c8a1-a4de-5f5f3e7e794d@2ndquadrant.com>
 <20200602160717.GA16329@momjian.us>
 <1a9904ee-b5f5-768b-25f4-5be52ee6ce7e@2ndquadrant.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1a9904ee-b5f5-768b-25f4-5be52ee6ce7e@2ndquadrant.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

On Thu, Jun  4, 2020 at 07:14:17PM +0200, Peter Eisentraut wrote:
> On 2020-06-02 18:07, 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.
> 
> One reason for that difference specifically is that vacuumlo is refentry
> which can generate its own link text like "vacuumlo(1)", and sepgsql is a
> sect1, which by default creates text like "Section 23.2", which perhaps
> someone wanted to override.

Yes, that makes sense, thanks.

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

  The usefulness of a cup is in its emptiness, Bruce Lee