Re: BUG #18766: not exists sometimes gives too few records

From: Jan Kort <jan(dot)kort(at)genetics(dot)nl>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18766: not exists sometimes gives too few records
Date: 2025-01-06 08:24:55
Message-ID: CACShyN-f+BX6tEmfCke2UTnVpU0GDjyAqwDOiBDWXd_OhBn-sg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thank you, upgrading to 16.6 worked.

Regards,

Jan

--
Met vriendelijke groet,

*Jan Kort |* *Ontwikkelaar*
R&D

E. jan(dot)kort(at)genetics(dot)nl <voornaam(dot)achternaam(at)genetics(dot)nl>
I. www.genetics.nl
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(at)gmail(dot)com> wrote:

> On Sat, 4 Jan 2025 at 06:28, PG Bug reporting form
> <noreply(at)postgresql(dot)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/
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2025-01-06 13:14:10 Re: BUG #18764: server closed the connection unexpectedly
Previous Message PG Bug reporting form 2025-01-06 08:24:33 BUG #18767: Inconsistency in result of a Plpgsql GET DIAGNOSTICS PG_CONTEXT instruction.