Re: Crash related to Shared Memory

From: Reshmithaa <reshmithaa(dot)b(at)zohocorp(dot)com>
To: "Tomas Vondra" <tomas(at)vondra(dot)me>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Crash related to Shared Memory
Date: 2026-02-16 11:54:34
Message-ID: 19c664d6527.32b1b9d371257.9050173181276080589@zohocorp.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Thanks for your reply, we will look into it.

Regards,
Reshmithaa B

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: "Reshmithaa"<reshmithaa(dot)b(at)zohocorp(dot)com>
Cc: "pgsql-hackers"<pgsql-hackers(at)postgresql(dot)org>
Date: Mon, 16 Feb 2026 16:13:07 +0530
Subject: Re: Crash related to Shared Memory

On 2/16/26 10:17, Reshmithaa wrote:
> Hi,
>
> > The second trace
>
> > unfortunately does not show what happened to PID 2037344 before it
>
> > crashes, which would be very interesting to know. Was it an OOM too?
>
> Kindly find the attachment below.
>

I have no idea what

LOG: 00000: PRIMITIVE NOT USED: map_pg_backend_pid
LOCATION: LogPrimFunctions, primitiveMgr.cpp:39
STATEMENT: select pg_backend_pid()

means, that's clearly something in your fork/extension.


regards

--
Tomas Vondra

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message VASUKI M 2026-02-16 12:19:53 Re: Optional skipping of unchanged relations during ANALYZE?
Previous Message Jakub Wartak 2026-02-16 11:34:17 Re: 64-bit wait_event and introduction of 32-bit wait_event_arg