From: Tom Lane <tgl@sss.pgh.pa.us>
To: Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17986: Inconsistent results of SELECT affected by btree index
Date: Wed, 21 Jun 2023 09:25:01 -0400
Message-ID: <3754266.1687353901@sss.pgh.pa.us> (raw)
In-Reply-To: <5095c4dd-dcce-1af2-0be3-9fba11db6c96@inf.ethz.ch>
References: <17986-6ebf8b5d2c3a4f6e@postgresql.org>
<e73bf331-7b1d-9808-d909-80688e318a88@enterprisedb.com>
<3689741.1687320665@sss.pgh.pa.us>
<5095c4dd-dcce-1af2-0be3-9fba11db6c96@inf.ethz.ch>
Zu-Ming Jiang <zuming.jiang@inf.ethz.ch> writes:
> Thanks for your information! I checked it again. Seems this bug can be
> reproduced when I used "quick-fix-for-bug-17985.patch" for bug 17985,
> but cannot be reproduced after I used "better-fix-for-bug-17985.patch".
> So it was fixed by the patch "better-fix-for-bug-17985.patch".
Oh, that's very interesting. There must be some other code path in
the executor that responds to the Hash node's allParams bit, and
doesn't do the right thing unless it's set. Not totally surprising
I guess; the quick-fix thing was definitely a hack.
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, zuming.jiang@inf.ethz.ch, tomas.vondra@enterprisedb.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17986: Inconsistent results of SELECT affected by btree index
In-Reply-To: <3754266.1687353901@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