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 ) id 1jftNe-0002VH-8Y for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jun 2020 22:58:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jftNc-0000V6-So for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jun 2020 22:58:04 +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 ) id 1jftNc-0000Uu-Li; Mon, 01 Jun 2020 22:58:04 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jftNW-0000V4-0T; Mon, 01 Jun 2020 22:58:03 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 051MvtD6506029; Mon, 1 Jun 2020 18:57:55 -0400 From: Tom Lane To: =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= cc: pgsql-docs@lists.postgresql.org, pgsql-hackers@lists.postgresql.org Subject: Re: Another modest proposal for docs formatting: catalog descriptions In-reply-to: References: <12984.1588643549@sss.pgh.pa.us> Comments: In-reply-to =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= message dated "Tue, 02 Jun 2020 00:40:09 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <506027.1591052275.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 01 Jun 2020 18:57:55 -0400 Message-ID: <506028.1591052275@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =3D?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?=3D writes: > I have spotted this change recently at progress monitoring devel docs ( > https://www.postgresql.org/docs/devel/progress-reporting.html#CREATE-IND= EX-PROGRESS-REPORTING). > Current version seems a little chaotic since there are multiple tables o= n > the same page with 2 mixed layouts. Older layout (for example v12 one - > https://www.postgresql.org/docs/12/progress-reporting.html#CREATE-INDEX-= PROGRESS-REPORTING) > is much easier to read for me. > Is this final change? I do not see any problem on this (progress > monitoring) page in old layout. Is there any example of problematic page= ? > Maybe there's a different way to solve this. For example instead of > in-lining long text as a column description, it should be possible to li= nk > to detailed description in custom paragraph or table. See description > column at table 27.22. at progress monitoring page for column "phase" fo= r > similar approach. I'm not planning on revisiting that work, no. And converting every table/view description table into two (or more?) tables sure doesn't sound like an improvement. Perhaps there's a case for reformatting the phase-description tables in the progress monitoring section to look more like the view tables. (I hadn't paid much attention to them, since they weren't causing PDF rendering problems.) On the other hand, you could argue that it's good that they don't look like the view tables, since the info they are presenting is fundamentally different. I don't honestly see much wrong with the way it is now. regards, tom lane