Subject: Re: Adding xreflable
To: Bruce Momjian <bruce@momjian.us>
References: <18482.1589549850@sss.pgh.pa.us>
 <20200515134900.GD3894@momjian.us> <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>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 PostgreSQL-documentation <pgsql-docs@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <1a9904ee-b5f5-768b-25f4-5be52ee6ce7e@2ndquadrant.com>
Date: Thu, 4 Jun 2020 19:14:17 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20200602160717.GA16329@momjian.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services