Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Jinhui Lai <jinhui-lai(at)foxmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
Date: 2025-07-25 16:22:12
Message-ID: CAKFQuwYn262QrZBOyxjg8qk8Ch-atvCfsEuAEgkLevz6HMwGGg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 25, 2025, 07:40 Jinhui Lai <jinhui-lai(at)foxmail(dot)com> wrote:

>
> #PG 17.5, 16, 15, 14, 13, 12, 11, 10...#
>
> #PG 17.0-17.4#
>

This would be an unintended change/regression when 17.0 came out that was
discovered and fixed in 17.5

Reverting back to long-established behavior should not be a surprising
action to see.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Hugo DUBOIS 2025-07-25 16:21:36 Re: Unexpected Standby Shutdown on sync_replication_slots change