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 1kDkZR-0005BX-ER for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Sep 2020 08:26:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kDkZQ-00033h-Br for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Sep 2020 08:26:12 +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 1kDkZQ-00033a-5g for pgsql-bugs@lists.postgresql.org; Thu, 03 Sep 2020 08:26:12 +0000 Received: from forward4-smtp.messagingengine.com ([66.111.4.238]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kDkZL-0004T8-Sf for pgsql-bugs@lists.postgresql.org; Thu, 03 Sep 2020 08:26:11 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id 344C3194211F; Thu, 3 Sep 2020 04:26:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 03 Sep 2020 04:26:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=FJdaJHRTqJCrzONkxIVf2zxZnKnianHf18EkvNOe4 Ro=; b=fDR2Z4Qvb/e/OGatBbDOGhlCPc/v/NjlivciN7LuOf+euBu2yHQzL/sbI CM6k+SiMabc+Z5z7JFDnKTAZ3KI4OYy8NRZeobSmqjtsBdQJj6WfE9OgQvUoIS8L wEvhdRsvy4GtEJc9X4wuxWObQuzMpnvPEmvj1xmBbkxRCFo5oxtkTJJWN3HneDSK NHm6jl0WZhciVODJitGYamZKCt/hoAiHt3DekaCkTAjqIcOn9ex931bhUDLypV1b YT8X4uZuuwknjPrBbS1Gi+AYkhLWUbmCIQ/uukz+3Vecy4KNNBiPFJmx/WXSppGE s5Zlr5ljYUeiTetuw/ddUL3XyLf9g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudeguddgtdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeelnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuggftrfgrthhtvghrnhepfeefudegueetteekveff keduhefgjedvgffggffhfeelueelvdfhvefhgfejveetnecuffhomhgrihhnpedvnhguqh hurggurhgrnhhtrdgtohhmnecukfhppeeluddrudegrddvfeefrdeffeenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvg hnthhrrghuthesvdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5b0ee921.dip0.t-ipconnect.de [91.14.233.33]) by mail.messagingengine.com (Postfix) with ESMTPA id 63987306005B; Thu, 3 Sep 2020 04:26:04 -0400 (EDT) Subject: Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows To: Daniel Verite , Jehan-Guillaume de Rorthais References: <8b6f61c4-eb21-484c-bdc6-e4b8e9f3ee62@manitou-mail.org> Cc: Thomas Munro , Peter Geoghegan , =?UTF-8?B?0KDQvtC80LDQvSDQm9C40YLQvtCy0YfQtdC90LrQvg==?= , PostgreSQL mailing lists From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <0df88ec9-90c6-54cb-ca63-7aafa5903b0c@2ndquadrant.com> Date: Thu, 3 Sep 2020 10:26:03 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <8b6f61c4-eb21-484c-bdc6-e4b8e9f3ee62@manitou-mail.org> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-09-03 09:41, Daniel Verite wrote: > Jehan-Guillaume de Rorthais wrote: > >> Maybe Daniel has some more experience feedback with other customizations > > No, I've just tried various other reorderings, and didn't find any other that > seems to have the same bug as latn-digit. > My tests consisted of indexing a large corpus of text and running the > index through amcheck. In this case I'm tempted to just leave it alone and write it off as a bug in ICU. We could potentially inspect the collator object at CREATE COLLATION time and issues warnings if we find something we know to be buggy. I don't think we want to make our code uglier and slower for normal uses to work around a bug in some niche feature in ICU. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services