Date: Fri, 13 Feb 2026 09:27:02 -0800
From: Noah Misch <noah@leadboat.com>
To: ranvis@gmail.com, pgsql-bugs@lists.postgresql.org
Cc: thomas.munro@gmail.com
Subject: Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value
 in PostgreSQL 15.16
Message-ID: <20260213172702.71@rfd.leadboat.com>
References: <19406-9867fddddd724fca@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19406-9867fddddd724fca@postgresql.org>
User-Agent: Mutt/2.2.12 (2023-09-09)
Archived-At: <https://www.postgresql.org/message-id/20260213172702.71%40rfd.leadboat.com>
Precedence: bulk

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.