| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Nikolay Shaplov <n(dot)shaplov(at)postgrespro(dot)ru>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Subject: | Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data |
| Date: | 2023-06-12 13:14:26 |
| Message-ID: | 1166430.1686575666@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> Anyway, I am not really convinced that we need to do anything here,
> either, knowing that v12 is able to fail early without relying on
> check_stack_depth(), and that v11 will be EOL'd in a couple of
> months.
Yeah, I couldn't get excited about it either. The fact that an
underflow check stops the loop seems a bit accidental. But the
proposed patch is not noticeably less magic than that, and who's
to say whether it doesn't cause unnecessary failures in other
cases besides the one given?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Shaplov | 2023-06-12 14:06:17 | Re: BUG #17962: postgresql 11 hangs on poly_contain with specific data |
| Previous Message | Alvaro Herrera | 2023-06-12 10:54:38 | Re: BUG #17967: [msvc-x86] Failed to build with error LNK2019: unresolved external symbol __BitScanReverse64 referen |