Re: The two "XML Fixes" patches still in need of review

From: Chapman Flack <chap(at)anastigmatix(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Markus Winand <markus(dot)winand(at)winand(dot)at>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Subject: Re: The two "XML Fixes" patches still in need of review
Date: 2019-03-23 23:46:23
Message-ID: 5C96C54F.5090901@anastigmatix.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/23/19 18:20, Chapman Flack wrote:
>> Perhaps it'd make sense under the XML section in datatype.sgml,
>> but I think I might lean to making it a new section in Appendix D
>> (SQL Conformance).
>
> Sounds like the option (4) I proposed back in [1]. I suppose it won't
> be much trouble to move.

The current structure of that appendix is: a few introductory paragraphs
(not wrapped in any <sect... ...>), followed by two <sect1>s that are
both autogenerated (the supported and unsupported features tables).

The <sect1>s become independent pages, in the HTML version.

- Move the XML limits/conformance section to a new <sect1> there?

- Before the autogenerated tables, or after them?

The un-<sect>ed intro paragraphs are preceded (in HTML) by a table
of contents, so the new section should show up there.

- Also add a mention (say, in the next-to-last intro paragraph) that
there are notes on the SQL/XML conformance that have their own
section (and link to it)? Or just let the generated ToC link be enough?

Regards,
-Chap

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2019-03-24 00:17:18 Re: [HACKERS] PATCH: multivariate histograms and MCV lists
Previous Message Tomas Vondra 2019-03-23 23:41:25 Re: [HACKERS] PATCH: multivariate histograms and MCV lists