From: | Zu-Ming Jiang <zuming(dot)jiang(at)inf(dot)ethz(dot)ch> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Cc: | <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #17986: Inconsistent results of SELECT affected by btree index |
Date: | 2023-06-21 07:22:38 |
Message-ID: | 5095c4dd-dcce-1af2-0be3-9fba11db6c96@inf.ethz.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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".
Best wishes,
Zuming
------------------------------------------------------------------------
*From:* Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
*Sent:* Wednesday, June 21, 2023 at 6:11 AM
*To:* Tomas Vondra
*Cc:* zuming(dot)jiang(at)inf(dot)ethz(dot)ch; pgsql-bugs(at)lists(dot)postgresql(dot)org
*Subject:* BUG #17986: Inconsistent results of SELECT affected by btree
index
> Tomas Vondra<tomas(dot)vondra(at)enterprisedb(dot)com> writes:
>> On 6/20/23 22:54, PG Bug reporting form wrote:
>>> My fuzzer finds a correctness bug in Postgres, which makes Postgres return
>>> inconsistent results.
>> I can't reproduce this with current master - perhaps one of the commits
>> since efeb12ef0b fixes this too?
> It looks like this is another manifestation of the hashjoin bug
> fixed in 45392626c.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2023-06-21 08:58:12 | Re: BUG #17949: Adding an index introduces serialisation anomalies. |
Previous Message | Richard Guo | 2023-06-21 07:20:50 | Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN |