From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Martin Kos <martin.kos@molecularhealth.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Bug in execution of EXISTS and IN clauses for large tables
Date: Tue, 22 Feb 2022 10:45:08 -0500
Message-ID: <701248.1645544708@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKFQuwZu-JTRz2R6+Xshm3-VzYEctzMo7hjj4Zn+dVcXypJHMA@mail.gmail.com>
References: <AM4PR0401MB2241616DE8A709B13019B0E59F3B9@AM4PR0401MB2241.eurprd04.prod.outlook.com>
<CAKFQuwbUMiHqeLZkCqqCL9gr0soREjprmTrQXJT1iQATfoNWEQ@mail.gmail.com>
<CAKFQuwZu-JTRz2R6+Xshm3-VzYEctzMo7hjj4Zn+dVcXypJHMA@mail.gmail.com>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> This seems like a decent report (haven’t played with it), still, version
> 11.1!
Indeed. I can't see any problem in 11.current --- for me, the first
four queries all give 44272445, the next 72002328, and the last two
60000000. So either we fixed it since 11.1, or the problem requires
some nondefault setting that wasn't mentioned. I'm not particularly
interested in bisecting to see where it was fixed.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, martin.kos@molecularhealth.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Bug in execution of EXISTS and IN clauses for large tables
In-Reply-To: <701248.1645544708@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox