Re: BUG #18832: Segfault in GrantLockLocal

From: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: tharakan(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: BUG #18832: Segfault in GrantLockLocal
Date: 2025-03-07 10:37:42
Message-ID: 202503071037.nrgp6vmhflcl@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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#Recording_Postgres_using_rr_Record_and_Replay_Framework

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Sabino Mullane 2025-03-07 14:23:40 Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
Previous Message Bertrand Drouvot 2025-03-07 07:02:08 Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string