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 1kPtfa-00034k-Dk for pgsql-docs@arkaria.postgresql.org; Tue, 06 Oct 2020 20:34:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kPtfW-00075G-VN for pgsql-docs@arkaria.postgresql.org; Tue, 06 Oct 2020 20:34:42 +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 1kPtfW-000759-Pj for pgsql-docs@lists.postgresql.org; Tue, 06 Oct 2020 20:34:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kPtfU-0002KF-4X for pgsql-docs@lists.postgresql.org; Tue, 06 Oct 2020 20:34:41 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 096KYbOf1998881; Tue, 6 Oct 2020 16:34:38 -0400 From: Tom Lane To: morgothko@gmail.com cc: pgsql-docs@lists.postgresql.org Subject: Re: nondeterministic collations and statistics and pattern matching In-reply-to: <160201076591.708.3970784784508799676@wrigleys.postgresql.org> References: <160201076591.708.3970784784508799676@wrigleys.postgresql.org> Comments: In-reply-to PG Doc comments form message dated "Tue, 06 Oct 2020 18:59:25 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1998879.1602016477.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 06 Oct 2020 16:34:37 -0400 Message-ID: <1998880.1602016477@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Doc comments form writes: > If exists statistic with nondeteministic collation inherited from column > collation then using pattern matching with collation will give an error. Yeah, that's a known problem we fixed months ago. > There is no information about it. (( Other than the 12.4 release note entry, you mean? > I have seen this thread > https://www.postgresql.org/message-id/flat/CAAFmbbOvfi%3DwMM%3D3qRsPunBS= Lb8BFREno2oOzSBS%3DmzfLPKABw%40mail.gmail.com > But I can't apply this patch for some reasons. What is your point exactly? You think the documentation should describe your unspecified reasons for not updating to 12.4? I'm afraid I'm not a telepath. regards, tom lane