Re: Query result differences between PostgreSQL 17 vs 16

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-04 07:30:26
Message-ID: CAMbWs4_35p90MAuEV_cU4s8bMyL1ci9oLbSgzmdTB_+umXvkSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 4, 2025 at 12:22 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

Pushed and back-patched to v17. The fix will be included in next
minor release (17.5).

Thanks
Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bertrand Drouvot 2025-03-04 07:38:14 Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
Previous Message Tender Wang 2025-03-04 06:58:01 Re: BUG #18830: ExecInitMerge Segfault on MERGE