| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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-03 22:38:14 |
| Message-ID: | 20200603223814.GA7455@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 이동욱 | 2020-06-04 13:20:01 | [PATCH] pg_dump: Add example and link for --encoding option |
| Previous Message | Fujii Masao | 2020-06-03 01:16:55 | Re: wal_init_zero and wal_recycle |