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 1jO2eG-0005PK-6q for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Apr 2020 17:13:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jO2eF-0001Ft-0U for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Apr 2020 17:13:27 +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 1jO2eE-0001Fm-QI for pgsql-hackers@lists.postgresql.org; Mon, 13 Apr 2020 17:13:26 +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 1jO2eC-0006dQ-Gi for pgsql-hackers@lists.postgresql.org; Mon, 13 Apr 2020 17:13:25 +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 03DHDNHO008692 for ; Mon, 13 Apr 2020 13:13:23 -0400 From: Tom Lane To: pgsql-hackers@lists.postgresql.org Subject: Poll: are people okay with function/operator table redesign? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8690.1586798003.1@sss.pgh.pa.us> Date: Mon, 13 Apr 2020 13:13:23 -0400 Message-ID: <8691.1586798003@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk As discussed in the thread at [1], I've been working on redesigning the tables we use to present SQL functions and operators. The first installment of that is now up; see tables 9.30 and 9.31 at https://www.postgresql.org/docs/devel/functions-datetime.html and table 9.33 at https://www.postgresql.org/docs/devel/functions-enum.html Before I spend more time on this, I want to make sure that people are happy with this line of attack. Comparing these tables to the way they look in v12, they clearly take more vertical space; but at least to my eye they're less cluttered and more readable. They definitely scale a lot better for cases where a long function description is needed, or where we'd like to have more than one example. Does anyone prefer the old way, or have a better idea? I know that the table headings are a bit weirdly laid out; hopefully that can be resolved [2]. regards, tom lane [1] https://www.postgresql.org/message-id/flat/9326.1581457869%40sss.pgh.pa.us [2] https://www.postgresql.org/message-id/6169.1586794603%40sss.pgh.pa.us