pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jürgen Purtz <juergen@purtz.de>
Cc: pgsql-docs@lists.postgresql.org
Cc: daelhithe@hotmail.com
Subject: Re: Documentation - chapter 52, system catalogs
Date: Tue, 05 May 2020 18:01:19 -0400
Message-ID: <28161.1588716079@sss.pgh.pa.us> (raw)
In-Reply-To: <aecbf4cf-9717-f83c-744e-4ed074989037@purtz.de>
References: <158860579891.671.9854443057028888145@wrigleys.postgresql.org>
	<aecbf4cf-9717-f83c-744e-4ed074989037@purtz.de>

=?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





view thread (4+ messages)  latest in thread

Message-ID: <28161.1588716079@sss.pgh.pa.us>
Permalink:  ../28161.1588716079@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28161.1588716079@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, juergen@purtz.de, pgsql-docs@lists.postgresql.org, daelhithe@hotmail.com
  Subject: Re: Documentation - chapter 52, system catalogs
  In-Reply-To: <28161.1588716079@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox