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 1n81m5-0002Iv-OL for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Jan 2022 15:12:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n81m4-0003zP-HX for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Jan 2022 15:12:24 +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 1n81m4-0003z0-8e for pgsql-bugs@lists.postgresql.org; Thu, 13 Jan 2022 15:12:24 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81ly-0004jb-Np for pgsql-bugs@lists.postgresql.org; Thu, 13 Jan 2022 15:12:23 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id AAC9E3201F1D; Thu, 13 Jan 2022 10:12:15 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 13 Jan 2022 10:12:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm1; bh=1tyEWycCe9v9b+RggARfpjE08a8vTNRHNIIpS4zrB 7Q=; b=e6UqvuiazaoTXOauZ9/Onj2FAOa9+rwwXXvOsgjs9IBHLbZz8rB/5DPiY 5nNUzEL826uDmszjCiz3ZEMcJkQQwKO4bSM8aBxLI+Kky7atcTNQQZEYCi5x+Dcd ZgAv1WK9k36IqwWXyvnQp/OIqQFlPvh/XHS875Rnau1g+j6ybO42p2D2e51AvKko pnjPLxKFDYpvjFTgPaZVJEWYt2YSbxF6w45mHUfJOOOGP37B/Tb6sVy2ehcG2AgK DXY0ljYFcH4ghY6teyJm25Z9GagSJ2Em98mteO1s0EsPA+P6e4GkDGPADzLvsm3l X/EKt8x0cmMn1ud7ivvQmv9Y3xY1Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtdefgdejfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 13 Jan 2022 10:12:13 -0500 (EST) Message-ID: <3869d444-2f89-f157-318d-a71ed712dcb7@enterprisedb.com> Date: Thu, 13 Jan 2022 16:12:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7 Content-Language: en-US To: Peter Geoghegan , eronenp@gmail.com, PostgreSQL mailing lists References: <17362-63967721ee562fa7@postgresql.org> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11.01.22 23:19, Peter Geoghegan wrote: > On Tue, Jan 11, 2022 at 3:16 AM PG Bug reporting form > wrote: >> When I query a table containing certain Unicode data, using an index that >> has certain collation, I get error message "could not find block containing >> chunk". This is fully reproducible on CentOS 7 using the official RPM. (I >> could not reproduce this on Oracle Linux 8, though): > > It looks like you're probably not using utf8 as your database > encoding, based on the stacktrace -- even though I would expect that > on your ICU version. What does "show server_encoding;" show you when > run from psql? > > My guess is that you can temporarily work around the bug (which looks > like a bug in our !HAVE_UCOL_STRCOLLUTF8 ICU support) by making sure > to use UTF-8 as the server encoding. It looks like the reporter's system is rhel7, which does not have HAVE_UCOL_STRCOLLUTF8, so it will use the other code independent of the encoding. There could very well be some subtle memory counting bug or similar in icu_to_uchar() perhaps. Needs more analysis.