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 1kDRX9-0008JQ-Uq for pgsql-bugs@arkaria.postgresql.org; Wed, 02 Sep 2020 12:06:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kDRX8-0002Eo-2v for pgsql-bugs@arkaria.postgresql.org; Wed, 02 Sep 2020 12:06:34 +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 1kDRX6-0002Eh-HO for pgsql-bugs@lists.postgresql.org; Wed, 02 Sep 2020 12:06:33 +0000 Received: from forward1-smtp.messagingengine.com ([66.111.4.223]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kDRWy-0001h5-8k for pgsql-bugs@lists.postgresql.org; Wed, 02 Sep 2020 12:06:31 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id 1C84119422A9; Wed, 2 Sep 2020 08:06:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 02 Sep 2020 08:06:22 -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=EYoGSYlhB5kdzrTUVBEfDr7xVPsG0xj4oe0mYF5JQ a0=; b=JV2rhaPQSK9egUvGmP4W/FgKpMPEdmgzNgz+Td/hKfr6d7BYQrtF7eKli gX2zyXBeemxbPb+NzH4GBbh/rbWAx7jIE76CkW4Ft8P11XyJfD2rj07j7VbKRaxJ OsBrVtJ2FSdTFMGPnvG5rWHFV0TZwTyfYC5qswEyM27r9OCoHmnmTyeRSjSTMXuJ ZUKyIYhfSYJBPub0EjCd5gl6HTmg0JgEz2OKY/MCezfbrLrTk0ZfjPjbVIMfXUhT p7/4xuWIS8dhcWhiBAaHzECI2SJkS6tiS+/YVqVpjhY/1QnyZ8XV/g28N4Il6qx8 fCzN73ZGWfrbUxPSCbXROA0O4RHtQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudefledggeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuggftrfgrthhtvghrnheptdevgeehtdejvdevvdel jeeuveejjedtleelgfekleefieekjeelgfektdduuedvnecuffhomhgrihhnpedvnhguqh hurggurhgrnhhtrdgtohhmnecukfhppeekjedrudejjedrjeejrdeltdenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvg hnthhrrghuthesvdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p57b14d5a.dip0.t-ipconnect.de [87.177.77.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 4332D30600B1; Wed, 2 Sep 2020 08:06:20 -0400 (EDT) Subject: Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows To: Jehan-Guillaume de Rorthais , Thomas Munro References: <153201618542.1404.3611626898935613264@wrigleys.postgresql.org> <20200610002933.6a6d482b@firost> Cc: Peter Geoghegan , =?UTF-8?B?0KDQvtC80LDQvSDQm9C40YLQvtCy0YfQtdC90LrQvg==?= , PostgreSQL mailing lists From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <4ea84116-4380-b12f-dcdf-7f2977ab2859@2ndquadrant.com> Date: Wed, 2 Sep 2020 14:06:18 +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: <20200610002933.6a6d482b@firost> Content-Type: text/plain; charset=utf-8; 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-06-10 00:29, Jehan-Guillaume de Rorthais wrote: > In the meantime, I've been working on various workarounds. The only one I found > is to use "fr-u-kr-latn-digit-kn" instead of "fr-u-kr-latn-digit". > Unfortunately, the two collations are not equivalent, but I believe it might be > useful in many case. What precisely is broken in the ICU library? All the examples so far refer to kr-latn-digit. Are all reorderings broken, or something specifically related to latn and/or digit? Are any collation customizations other than reorderings affected? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services