Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i6Ihj-0002gR-BG for pgsql-hackers@arkaria.postgresql.org; Fri, 06 Sep 2019 18:11:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i6Ihh-0001XQ-5V for pgsql-hackers@arkaria.postgresql.org; Fri, 06 Sep 2019 18:11:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i6Ihg-0001T4-Q2 for pgsql-hackers@lists.postgresql.org; Fri, 06 Sep 2019 18:11:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1i6Iha-0006yI-Br for pgsql-hackers@lists.postgresql.org; Fri, 06 Sep 2019 18:11:23 +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 x86IBCup004172; Fri, 6 Sep 2019 14:11:12 -0400 From: Tom Lane To: Alvaro Herrera from 2ndQuadrant cc: Andrew Gierth , pgsql-hackers@lists.postgresql.org Subject: Re: SQL-spec incompatibilities in similar_escape() and related stuff In-reply-to: <20190906170132.GA14506@alvherre.pgsql> References: <20190906170132.GA14506@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera from 2ndQuadrant message dated "Fri, 06 Sep 2019 13:01:32 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4170.1567793472.1@sss.pgh.pa.us> Date: Fri, 06 Sep 2019 14:11:12 -0400 Message-ID: <4171.1567793472@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera from 2ndQuadrant writes: > This discussion seems to have died down. Apparently we have three > directions here, from three different people. Are we doing anything? I don't really want to do anything beyond the patch I submitted in this thread (at <32617.1558649424@sss.pgh.pa.us>). That's what the CF entry is for, IMO. I'm not excited about the change-of-keywords business, but if someone else is, they should start a new CF entry about that. regards, tom lane