Feedback-ID: ia2694551:Fastmail
Date: Wed, 11 Oct 2023 18:39:43 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: splarv@ya.ru, pgsql-docs@lists.postgresql.org
Subject: Re: 31.7.1. Initial Snapshot
Message-ID: <202310111639.urgm5z2ri2jp@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <169704184201.656.8380020202123281494@wrigleys.postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/202310111639.urgm5z2ri2jp%40alvherre.pgsql>
Precedence: bulk

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. Initial Snapshot" on
> https://www.postgresql.org/docs/16/logical-replication-architecture.html

Yeah, that looks a bit ugly ... but actually the first line you see with
that text is the table-of-contents for the page.  Since there's a single
section in that chapter, the TOC looks like a section title.  You can
probably find several pages in the docs where this happens.

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 the TOC at all.  I have no idea how to implement such
a fix, or whether it'd be really acceptable after all.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"After a quick R of TFM, all I can say is HOLY CR** THAT IS COOL! PostgreSQL was
amazing when I first started using it at 7.2, and I'm continually astounded by
learning new features and techniques made available by the continuing work of
the development team."
Berend Tober, http://archives.postgresql.org/pgsql-hackers/2007-08/msg01009.php