| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | ranvis(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | thomas(dot)munro(at)gmail(dot)com |
| Subject: | Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16 |
| Date: | 2026-02-13 17:27:02 |
| Message-ID: | 20260213172702.71@rfd.leadboat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Feb 13, 2026 at 07:46:22AM +0000, PG Bug reporting form wrote:
> After upgrading from PostgreSQL 15.15 to 15.16, substring(text) raises:
> >ERROR: invalid byte sequence for encoding "UTF8": 0xe6 0x97
> on valid UTF-8 text stored in a TOAST-compressed column.
> user=> select substring(data from 1 for 1) from toast_repro;
> ERROR: 22021: invalid byte sequence for encoding "UTF8": 0xe6 0x97
Thanks for the report. That is a bug and a regression; I regret missing it
during review. The substring operation works by taking a 4-byte slice from
the toasted value (4 bytes being the max length of a UTF8 char in PostgreSQL),
the finding the actual first character within those bytes. However, it
incorrectly requires those four bytes to be a valid UTF8 string. I'll start
on a fix.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-02-13 19:05:56 | BUG #19408: Bad plan for UNION ALL subquery with outer WHERE, ORDER BY, LIMIT, and separate indexes |
| Previous Message | Marcel Hofstetter | 2026-02-13 16:44:16 | Re: BUG #19404: manpages are missing in 18.x source.tar.gz |