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 1pwNrV-000349-QD for pgsql-docs@arkaria.postgresql.org; Tue, 09 May 2023 13:58:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pwNrU-0005NA-OY for pgsql-docs@arkaria.postgresql.org; Tue, 09 May 2023 13:58:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pwNrU-0005N1-HW for pgsql-docs@lists.postgresql.org; Tue, 09 May 2023 13:58:40 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pwNrS-001aVp-0Q for pgsql-docs@postgresql.org; Tue, 09 May 2023 13:58:39 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 30EBD2F84A2F for ; Tue, 9 May 2023 15:58:37 +0200 (CEST) Received: from s899.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 21C772E295D3; Tue, 9 May 2023 15:58:37 +0200 (CEST) Received: from s898.loopia.se (unknown [172.22.191.5]) by s899.loopia.se (Postfix) with ESMTP id 1FF542C8BACE; Tue, 9 May 2023 15:58:37 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s981.loopia.se ([172.22.191.6]) by s898.loopia.se (s898.loopia.se [172.22.190.17]) (amavisd-new, port 10024) with UTF8LMTP id Cpt1_Hc4cVT5; Tue, 9 May 2023 15:58:36 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s981.loopia.se (Postfix) with ESMTPSA id 7C89F22B175D; Tue, 9 May 2023 15:58:36 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: tables on pgbench man page look garbled From: Daniel Gustafsson In-Reply-To: <3e17d64b-863d-aa8d-334d-0d857e571b63@enterprisedb.com> Date: Tue, 9 May 2023 15:58:36 +0200 Cc: pgsql-docs Content-Transfer-Encoding: quoted-printable Message-Id: References: <3e17d64b-863d-aa8d-334d-0d857e571b63@enterprisedb.com> To: Peter Eisentraut X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 9 May 2023, at 15:40, Peter Eisentraut = wrote: >=20 > The tables "pgbench Operators" and "pgbench Functions" on the pgbench = man page (the actual man page, not the HTML reference page) look pretty = garbled. Also, on macOS, man prints a warning that the page is = invalidly formatted. But the garbledness happens on Linux as well, for = example. Apparently, our custom table layout doesn't map properly to = the man format. But for example, the earlier table "pgbench Automatic = Variables", which doesn't use the custom table layout, looks fine. = Anyone feel like looking into this further? Can you post a screenshot of what it looks like? I just built the = manpages from HEAD on macOS and while they report the UNSUPP error the table = itself looks like I would expect it to. -- Daniel Gustafsson