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 1jO7vW-0001Ra-57 for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Apr 2020 22:51:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jO7vU-0005i2-Qu for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Apr 2020 22:51:36 +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 1jO7vU-0005hv-KG for pgsql-hackers@lists.postgresql.org; Mon, 13 Apr 2020 22:51:36 +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 1jO7vS-0000yY-Ej; Mon, 13 Apr 2020 22:51:35 +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 03DMpXsM032161; Mon, 13 Apr 2020 18:51:33 -0400 From: Tom Lane To: "Jonathan S. Katz" cc: pgsql-hackers@lists.postgresql.org Subject: Re: Poll: are people okay with function/operator table redesign? In-reply-to: References: <8691.1586798003@sss.pgh.pa.us> Comments: In-reply-to "Jonathan S. Katz" message dated "Mon, 13 Apr 2020 18:33:58 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <32159.1586818293.1@sss.pgh.pa.us> Date: Mon, 13 Apr 2020 18:51:33 -0400 Message-ID: <32160.1586818293@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Jonathan S. Katz" writes: > I think one thing that was throwing me off was having the function > signature before the description. I would recommend flipping them: have > the function description first, followed by signature, followed be > examples. I think that follows the natural flow more of what one is > doing when they look up the function. The trouble with that is it doesn't work very well when we have multiple similarly-named functions with different signatures. Consider what the two enum_range() entries in 9.33 will look like, for example. I think we need the signature to establish which function we're talking about. > There are probably some things we can do with shading on the pgweb side > to make items more distinguishable, I don't think that would be too > terrible to add. Per David's earlier comment, it seems like alternating backgrounds might be feasible if we can get it down to one per function, as the version I just posted has. regards, tom lane