From: Álvaro Herrera <alvherre@alvh.no-ip.org>
To: Richard Guo <guofenglinux@gmail.com>
Cc: tharakan@gmail.com, pgsql-bugs@lists.postgresql.org, Heikki Linnakangas <hlinnaka@iki.fi>
Subject: Re: BUG #18832: Segfault in GrantLockLocal
Date: Fri, 7 Mar 2025 11:37:42 +0100
Message-ID: <202503071037.nrgp6vmhflcl@alvherre.pgsql> (raw)
In-Reply-To: <CAMbWs4-+mmAsNM=ewbYWTKSkpXDGuj_toeEO=sKwa4YGaqfD=w@mail.gmail.com>
On 2025-Mar-07, Richard Guo wrote:
> 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.
One way to capture this might be to run the problem workload under rr
enough times until it reproduces, and then it can then be replayed under
the debugger.
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#...
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, guofenglinux@gmail.com, hlinnaka@iki.fi
Subject: Re: BUG #18832: Segfault in GrantLockLocal
In-Reply-To: <202503071037.nrgp6vmhflcl@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox