Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1jW5d0-0004de-Fc
	for pgsql-docs@arkaria.postgresql.org; Tue, 05 May 2020 22:01:26 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1jW5cy-000394-VP
	for pgsql-docs@arkaria.postgresql.org; Tue, 05 May 2020 22:01:24 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jW5cy-00038x-PU
	for pgsql-docs@lists.postgresql.org; Tue, 05 May 2020 22:01:24 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jW5cw-0002n9-Oa
	for pgsql-docs@lists.postgresql.org; Tue, 05 May 2020 22:01:23 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 045M1JaZ028162;
	Tue, 5 May 2020 18:01:19 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de>
cc: pgsql-docs@lists.postgresql.org, daelhithe@hotmail.com
Subject: Re: Documentation - chapter 52, system catalogs
In-reply-to: <aecbf4cf-9717-f83c-744e-4ed074989037@purtz.de>
References: <158860579891.671.9854443057028888145@wrigleys.postgresql.org>
 <aecbf4cf-9717-f83c-744e-4ed074989037@purtz.de>
Comments: In-reply-to =?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de>
	message dated "Tue, 05 May 2020 12:20:44 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28160.1588716079.1@sss.pgh.pa.us>
Date: Tue, 05 May 2020 18:01:19 -0400
Message-ID: <28161.1588716079@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

=?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de> writes:
> The attached patch contains:
> - for "System Catalog": moving paragraphs from bottom of 51. to top of 
> 51.1. (in PG 11 it is chapter 52); explanation that "System Catalog" is 
> a synonym for a concrete schema and its tables.
> - for "Information Schema": moving paragraphs from bottom of 36. to 
> middle of 36.1. ; an explanation that it relies on the system catalog; 
> change the title of 36.1. to "Overview" in correlation with "System 
> Catalog".

I don't like this patch much; it seems to me that from a semantic
standpoint, it's making things worse not better.  Text that's ahead
of the first <sect1> is more important than the text after it,
or should be.

I don't deny that we have a problem here: in the website rendering,
that text tends to be pushed down out of sight by the chapter's
sub-table-of-contents.  But that issue exists for every chapter
that's got more than a couple of sections.  We shouldn't hack
around it for just these two chapters.  Chapter 9 and Appendix F
are additional examples where this is a fairly urgent issue.

I wonder if we should just drop the sub-table-of-contents material.
(I'm assuming DocBook can be coerced to do that; but since the PDF
output has no such material, it seems like it ought to be possible.)

Or ... is there a way to postpone it to the bottom of the page,
ie just before the first <sect1>, instead of having it in front
of the chapter preface?

The same issue exists for the sub-sub-tables-of-contents for <sect1>s,
though it's less bad because few of those have grown enormous lists
of <sect2>'s.

			regards, tom lane