| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zu-Ming Jiang <zuming(dot)jiang(at)inf(dot)ethz(dot)ch> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17986: Inconsistent results of SELECT affected by btree index |
| Date: | 2023-06-21 13:25:01 |
| Message-ID: | 3754266.1687353901@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Zu-Ming Jiang <zuming(dot)jiang(at)inf(dot)ethz(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 270246512 | 2023-06-21 14:14:23 | Re:Re: BUG #17987: zypper refresh failed when installed the postgresql |
| Previous Message | Laurenz Albe | 2023-06-21 11:17:27 | Re: BUG #17987: zypper refresh failed when installed the postgresql |