Re: BUG #19412: Wrong query result with not null constraint

From: Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #19412: Wrong query result with not null constraint
Date: 2026-02-20 10:54:10
Message-ID: 96b4135a-1b32-4c05-91f5-61c5e2559f73@postgrespro.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2/20/26 12:57, Richard Guo wrote:
> ... and then pushed and back-patched to v16.

Thank you!

> Thank you, Sergey, for the report and the excellent self-contained
> repro query. This is a great catch. (I'm curious how you found this
> bug -- was it from a production query or a fuzzing tool?)

The bug was encountered by our customer upgrading to v17 and my
colleague passed this repro to me.

--
Sergey Shinderuk https://postgrespro.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message ludovitkramar 2026-02-20 23:58:59 BUG: SUBSTRING on TOASTed text returns "invalid byte sequence for encoding UTF8: 0xc3"
Previous Message Ishan joshi 2026-02-20 10:39:28 Re: BUG #19396: Standby and DR site replication broken with PANIC: WAL contains references to invalid pages messge