Re: Query result differences between PostgreSQL 17 vs 16

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, Ronald Cruz <cruz(at)rentec(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Ford <pford(at)rentec(dot)com>, "Aaron J(dot) Garcia" <agarcia(at)rentec(dot)com>
Subject: Re: Query result differences between PostgreSQL 17 vs 16
Date: 2025-03-03 15:22:31
Message-ID: 3650809.1741015351@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> Here is an updated patch, which also includes the test case you found
> proving the no-clone-quals limitation in restriction_is_always_false
> is also needed.

LGTM.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tender Wang 2025-03-03 15:46:11 Re: BUG #18830: ExecInitMerge Segfault on MERGE
Previous Message Bertrand Drouvot 2025-03-03 08:50:54 Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string