public inbox for [email protected]  

help / color / mirror / Atom feed

From: Daniel Gustafsson <[email protected]>
To: Robert Haas <[email protected]>
Cc: Rahila Syed <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Fujii Masao <[email protected]>
Cc: Tomas Vondra <[email protected]>
Subject: Re: Prevent an error on attaching/creating a DSM/DSA from an interrupt handler.
Date: Thu, 1 May 2025 12:08:09 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+TgmoYWbjZ9k1kuia2CXfJ3+b6G+=AayzU-hsXdtvGLgstFcw@mail.gmail.com>
References: <CA+TgmoYWbjZ9k1kuia2CXfJ3+b6G+=AayzU-hsXdtvGLgstFcw@mail.gmail.com>

> On 1 May 2025, at 00:04, Robert Haas <[email protected]> wrote:
> 
> On Wed, Apr 30, 2025 at 5:24 PM Daniel Gustafsson <[email protected]> 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.

Thanks for review, I’m currently travelling over the extended weekend but will rework the approach shortly when back at the office.

./daniel

view thread (2+ messages)

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Prevent an error on attaching/creating a DSM/DSA from an interrupt handler.
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox