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 1jNqpo-00067W-1a for pgsql-docs@arkaria.postgresql.org; Mon, 13 Apr 2020 04:36:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jNqpk-0000bj-Vz for pgsql-docs@arkaria.postgresql.org; Mon, 13 Apr 2020 04:36:32 +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 1jNqpk-0000bc-Os for pgsql-docs@lists.postgresql.org; Mon, 13 Apr 2020 04:36:32 +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 ) id 1jNqpd-0000fl-97 for pgsql-docs@lists.postgresql.org; Mon, 13 Apr 2020 04:36:31 +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 03D4aMPA010439; Mon, 13 Apr 2020 00:36:23 -0400 From: Tom Lane To: Corey Huinker cc: Alexander Lakhin , pgsql-docs@lists.postgresql.org Subject: Re: Getting our tables to render better in PDF output In-reply-to: References: <20200212221818.GA15503@alvherre.pgsql> <23574.1581555393@sss.pgh.pa.us> <10810.1581883655@sss.pgh.pa.us> <5d1f5b72-1b4a-6e15-6730-d94e2252a073@gmail.com> <525a6c9e-a4e2-cd8f-54b6-b69f40d70289@gmail.com> <701.1586638307@sss.pgh.pa.us> <6162.1586644916@sss.pgh.pa.us> Comments: In-reply-to Corey Huinker message dated "Sun, 12 Apr 2020 01:31:22 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10437.1586752582.1@sss.pgh.pa.us> Date: Mon, 13 Apr 2020 00:36:22 -0400 Message-ID: <10438.1586752582@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Corey Huinker writes: > On Sat, Apr 11, 2020 at 6:41 PM Tom Lane wrote: >> Don't have a strong opinion about that, but it'd sure be a lot of new >> anchors. > So I can't speak to any scalability issues for adding a bunch of refs, I did a quick check by adding id tags to all 700-or-so s in func.sgml (don't get excited, it was a perl one-liner that just added random id strings). The runtime difference for building the HTML docs seems to be under 1%, and negligible for PDF output. So it looks like we don't have to worry about scalability of tagging all the functions. regards, tom lane