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 1jQXIW-0007Ke-AN for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Apr 2020 14:21:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jQXIU-0002Vr-Fa for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Apr 2020 14:21:18 +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 1jQXIU-0002Vk-93 for pgsql-hackers@lists.postgresql.org; Mon, 20 Apr 2020 14:21:18 +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 1jQXIS-0001Ba-8V for pgsql-hackers@lists.postgresql.org; Mon, 20 Apr 2020 14:21:17 +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 03KELElY011668; Mon, 20 Apr 2020 10:21:14 -0400 From: Tom Lane To: Victor Yegorov cc: PostgreSQL Developers Subject: Re: Poll: are people okay with function/operator table redesign? In-reply-to: References: <20200416230304.GA28390@alvherre.pgsql> <17560.1587083109@sss.pgh.pa.us> <26009.1587302581@sss.pgh.pa.us> <10100.1587315592@sss.pgh.pa.us> Comments: In-reply-to Victor Yegorov message dated "Mon, 20 Apr 2020 13:38:46 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <11666.1587392474.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 20 Apr 2020 10:21:14 -0400 Message-ID: <11667.1587392474@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Victor Yegorov writes: > While table 9.5 with functions looks quite nice, I quite dislike 9.4 with > operators. > Previously, I could lookup operator in the leftmost column and read on. > Right now I have to look through the whole table (well, not really, but > still) to find the operator. Aside from the alternatives already discussed, the only other idea that's come to my mind is to write operator entries in a style like || as in: text || text → text Concatenates the two strings. 'Post' || 'greSQL' → PostgreSQL Not sure that that's any better, but it is another alternative. regards, tom lane