Re: Prevent an error on attaching/creating a DSM/DSA from an interrupt handler.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Rahila Syed <rahilasyed90(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: Prevent an error on attaching/creating a DSM/DSA from an interrupt handler.
Date: 2025-04-30 22:03:49
Message-ID: CA+TgmoYWbjZ9k1kuia2CXfJ3+b6G+=AayzU-hsXdtvGLgstFcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 30, 2025 at 5:24 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> Attached is a current v4 with a few small tweaks.

Sorry to turn up late here, but I strongly disagree with the notion
that this is a bug in the DSM or DSA code. It seems to me that it is
the caller's responsibility to provide a valid resource owner, not the
job of the called code to ignore the resource owner when it's
unusable. I suspect that there are many other parts of the system that
rely on the ResourceOwner machinery which likewise assume that the
ResourceOwner that they are passed is valid.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-04-30 22:26:47 Re: Fix slot synchronization with two_phase decoding enabled
Previous Message Robert Haas 2025-04-30 22:00:45 Re: pgsql: Add function to get memory context stats for processes