Quick Links

Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16

From:	Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To:	Noah Misch <noah(at)leadboat(dot)com>
Cc:	ranvis(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject:	Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
Date:	2026-02-14 08:15:45
Message-ID:	CA+hUKGJ2Azp21o+Vm3enjA6WNao_=Xyu_EFjZwoc=YqSg+LjXQ@mail.gmail.com
Views:	Whole Thread \| Raw Message \| Download mbox \| Resend email
Thread:
Lists:	pgsql-bugs

On Sat, Feb 14, 2026 at 6:38 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
> [mblen-valgrind-after-report-v1.patch]

LGTM. The new valgrind check should clearly be after the new non-local exit.

Studying the other patch...

In response to

Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16 at 2026-02-14 05:38:21 from Noah Misch

Responses

Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16 at 2026-02-14 19:07:22 from Thomas Munro

Browse pgsql-bugs by date

	From	Date	Subject
Next Message	Michael Banck	2026-02-14 09:05:02	Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Previous Message	Noah Misch	2026-02-14 05:38:21	Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16