Alvaro Herrera writes:
> On 2023-Oct-11, David G. Johnston wrote:
>> Improved formatting overall for the chapter ToC has merit.
> Great ...
+1. I've been annoyed by this ambiguity too. I agree that
artificially forcing pages to have at least two subsections
isn't a good fix.
On 2023-Oct-11, David G. Johnston wrote:
> Or move 4 paragraphs of introductory material into its own section so that
> there are two sections and a brief sentence for an intro.
We have lots of other places where this (single-entry TOCs) happens. I
don't think we want to add spurious tags in al
On Wed, Oct 11, 2023 at 9:41 AM Alvaro Herrera
wrote:
> Maybe a fix for this would be to style chapter TOCs in some way that
> makes it clear that they are TOCs -- for example, add a (subtly) visible
> bounding box, or something. Or maybe if a chapter has a single section,
> just do not print th
On 2023-Oct-11, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/logical-replication-architecture.html
> Description:
>
> There are dublicated section named "31.7.1. Initi
On Wed, Oct 11, 2023 at 9:32 AM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page:
> https://www.postgresql.org/docs/16/logical-replication-architecture.html
> Description:
>
> There are dublicated section named &quo
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/logical-replication-architecture.html
Description:
There are dublicated section named "31.7.1. Initial Snapshot" on
https://www.postgresql.org/docs/16/logical-r
