| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | eronenp(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Subject: | Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7 |
| Date: | 2022-01-11 22:19:38 |
| Message-ID: | CAH2-Wz=K4AZqQentZ0VgYjk3RpRA8n6oVrt2Cv0b977dA4qrDQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jan 11, 2022 at 3:16 AM PG Bug reporting form
<noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-01-11 22:46:02 | BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink |
| Previous Message | Peter Geoghegan | 2022-01-11 21:15:34 | Re: When Update balloons memory |