From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
---|---|
To: | tharakan(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Subject: | Re: BUG #18832: Segfault in GrantLockLocal |
Date: | 2025-03-07 00:49:53 |
Message-ID: | CAMbWs4-+mmAsNM=ewbYWTKSkpXDGuj_toeEO=sKwa4YGaqfD=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Mar 6, 2025 at 9:57 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> While running some tests on a recent HEAD commit (d4a6c847ca), I got 3
> segfaults today (2 for ALTER DEFAULT PRIVILEGES and 1 FOR SELECT
> pg_drop_replication_slot()). I just happen to be testing this commit, so I
> am not suspecting this commit to be the cause, but what I can add is that
> I've run similar workloads last month and these crashes are too close to be
> a coincidence - in effect I wouldn't be surprised if this is owing to a
> recent change.
I encountered the same issue months ago and reported it here [1].
Heikki suspected that commit 3c0fd64fec might be the culprit.
Unfortunately, we haven't been able to track it down because we
couldn't find a reliable way to reproduce it.
Your report shows that this issue still exists on master. I think it
would be great if we could take this chance to trace it down to the
root cause.
Thanks
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2025-03-07 01:13:27 | Re: Memoize in between of two JOIN nodes |
Previous Message | Masahiko Sawada | 2025-03-06 19:35:58 | Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string |