Re: BUG #18766: not exists sometimes gives too few records - Mailing list pgsql-bugs

From Jan Kort
Subject Re: BUG #18766: not exists sometimes gives too few records
Date
Msg-id CACShyN-f+BX6tEmfCke2UTnVpU0GDjyAqwDOiBDWXd_OhBn-sg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18766: not exists sometimes gives too few records  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-bugs
Thank you, upgrading to 16.6 worked.

Regards,

Jan

--

Met vriendelijke groet,

Jan Kort | Ontwikkelaar
R&D

T. (+31) 36 54 00 850
M. (+31) 6 0000 00 00
A. Postbus 1268, 1300 BG Almere
B. Bouwmeesterweg 8, 1333 LC Almere

Aanwezig: ma | di | woe | do | vrij


On Sat, 4 Jan 2025 at 13:15, David Rowley <dgrowleyml@gmail.com> wrote:
On Sat, 4 Jan 2025 at 06:28, PG Bug reporting form
<noreply@postgresql.org> wrote:
> All databases are running PostgreSQL 16.2 on Windows, to be specific:

You should really be running 16.6.   There was a bug fixed in 16.4
that sounds very likely to solve your problem, namely:

"Avoid incorrect results from Merge Right Anti Join plans (Richard
Guo)".  See [1]

If you still get wrong results with 16.6, please let us know.

David

[1] https://www.postgresql.org/docs/release/16.4/

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18767: Inconsistency in result of a Plpgsql GET DIAGNOSTICS PG_CONTEXT instruction.
Next
From: Richard Guo
Date:
Subject: Re: BUG #18764: server closed the connection unexpectedly