| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SIGSEGV in GrantLockLocal() |
| Date: | 2024-12-18 09:46:26 |
| Message-ID: | CAMbWs48MFZfLe2eKOP9k2Ub2oNq7V-NAPpLALYKx1uPUdoNg9Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 18, 2024 at 5:36 PM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> I don't know how that can happen, but I suspect commit 3c0fd64fec
> because it changed things in that area. If you can find a way to
> reproduce that even sporadically, that would be very helpful!
Thank you for the information. I'll try running the same pattern of
fuzz testing based on the code before commit 3c0fd64fec to see if this
SIGSEGV happens again. I'm not sure how helpful this will be, though,
as it usually takes several days, or sometimes weeks, to trigger this
issue.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-12-18 10:21:35 | Re: POC: make mxidoff 64 bits |
| Previous Message | Peter Eisentraut | 2024-12-18 09:42:37 | Re: pure parsers and reentrant scanners |