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 1jRftE-0007lK-Ae for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2020 17:43:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jRftB-00041D-Hw for pgsql-hackers@arkaria.postgresql.org; Thu, 23 Apr 2020 17:43:53 +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 1jRftB-000415-5b for pgsql-hackers@lists.postgresql.org; Thu, 23 Apr 2020 17:43:53 +0000 Received: from mail-qk1-x735.google.com ([2607:f8b0:4864:20::735]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jRft6-0005uA-EF for pgsql-hackers@lists.postgresql.org; Thu, 23 Apr 2020 17:43:52 +0000 Received: by mail-qk1-x735.google.com with SMTP id j4so7262080qkc.11 for ; Thu, 23 Apr 2020 10:43:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=fojKSAJOctm50lbdVl/azlGecvS1LborDyGzYikJtd0=; b=Rce13Bb1ykoMGrQ7jIUUYQqOxtafzR+sL+BkXEYsMdzaW7iIAN7B7HUOfvXD5SZKiC GOA5dRUA0kQecipqD78tJMNQcLkthbvGSVchmDl4epdICvUWNj6zA7zL4JqoLdMfRF91 MGnQ3M11TjrBIGEvpBu+Y/gpFX8wYkh/9kyZaKHejC/kbUKQK3TXwMLuBOLilPxMtfCN 0pzGzMBAze4SguNX70r7i5J2EsDO7vrB2VTkR4G/eNfeIIgQ3cJbUaX3JerIZNVFgW6t sTAcdaINWpXBBA/k3p0ztVgGQRG+q9bm50mYZ5ocSS7Ydcjpi/IY4Z00JsEs6KTAOMsU 8RgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=fojKSAJOctm50lbdVl/azlGecvS1LborDyGzYikJtd0=; b=WukIP02Hg2i7+Km3R0Wx7c7V3Z0SCSmRuesYX72GojcDz2ubMFJbcL/uNXH/z8Zwy4 nv5LIi8kXoKp/xZSNl39ABjd7L9pTMg1mnCkTgY/cHR4qIiepRGohnLRc6KKud5YJ+1h fMkfLa3DtSRznKzrh+vgjfx47CcY6wKxB3FQ+R1TUYhaymH3RWJaymJQzjADcNpIQzr5 9OrWtozQmYlVXqkP8/dRyEsB+2FPPvSoPdBrq5WqM8zdLOLwGm/aox/sXBALNKQcl2RI eugc1eoijlaGKnHqxrDdZSUGoaY5su9wbfVKRGstQhoxuetkeqnD6brFdCeOvh9kdEKa zzHg== X-Gm-Message-State: AGi0PuaESiAov/L/eUnMNCdAmVPA0HaOyE2JMrxKY6qAfsEAmlOVyQVp kQMRlP0POf7uLJq+4CQy8dguEA== X-Google-Smtp-Source: APiQypJU43JYu8wo0wgIJMb4ovv5Yv2CF5VIqXEqPaptWlFxFLWIyjbcn6AF2tJk+XJsUdg7LqiY+w== X-Received: by 2002:a05:620a:144c:: with SMTP id i12mr4791240qkl.416.1587663826697; Thu, 23 Apr 2020 10:43:46 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id v23sm1943250qkv.55.2020.04.23.10.43.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Apr 2020 10:43:46 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 028853014D3; Thu, 23 Apr 2020 13:43:43 -0400 (-04) Date: Thu, 23 Apr 2020 13:43:43 -0400 From: Alvaro Herrera To: Tom Lane Cc: Bruce Momjian , Peter Eisentraut , Robert Haas , Steven Pousty , Pavel Stehule , Isaac Morland , Pierre Giraud , PostgreSQL Developers Subject: Re: Poll: are people okay with function/operator table redesign? Message-ID: <20200423174343.GA16996@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <15395.1587660207@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk If we're doing nicer markup+CSS for this, then it might make sense to find a better solution for this kind of entry with multiple signatures (which was already an issue in the previous version): text || anynonarray or anynonarray || text → text Converts the non-string input to text, then concatenates the two strings. (The non-string input cannot be of an array type, because that would create ambiguity with the array || operators. If you want to concatenate an array's text equivalent, cast it to text explicitly.) 'Value: ' || 42 → Value: 42 I think it would make sense to split the first line to put each of the two signatures on their own line. So it would look like this: text || anynonarray anynonarray || text → text Converts the non-string input to text, then concatenates the two strings. (The non-string input cannot be of an array type, because that would create ambiguity with the array || operators. If you want to concatenate an array's text equivalent, cast it to text explicitly.) 'Value: ' || 42 → Value: 42 Another example: to_ascii ( string text [, encoding name or integer ] ) → text should be (I think): to_ascii ( string text [, encoding name ] ) → text to_ascii ( string text [, integer ] ) → text -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services