| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Adding xreflable |
| Date: | 2020-06-11 22:38:45 |
| Message-ID: | 20200611223845.GB2507@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-06-12 02:45:43 | Re: Default setting for enable_hashagg_disk |
| Previous Message | Bruce Momjian | 2020-06-11 22:38:36 | Re: Adding xreflable |