Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7 - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
Date
Msg-id CAH2-Wz=K4AZqQentZ0VgYjk3RpRA8n6oVrt2Cv0b977dA4qrDQ@mail.gmail.com
Whole thread Raw
In response to BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7  (Pasi Eronen <eronenp@gmail.com>)
Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-bugs
On Tue, Jan 11, 2022 at 3:16 AM PG Bug reporting form
<noreply@postgresql.org> 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.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: When Update balloons memory
Next
From: PG Bug reporting form
Date:
Subject: BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink