Re: Eliminating SPI / SQL from some RI triggers - take 3 - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Eliminating SPI / SQL from some RI triggers - take 3
Date
Msg-id CA+HiwqFh_CMi95g2-W259i216_MxDMuOUcR+vrA8VqSTf8KLXA@mail.gmail.com
Whole thread Raw
In response to Re: Eliminating SPI / SQL from some RI triggers - take 3  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Eliminating SPI / SQL from some RI triggers - take 3
List pgsql-hackers
On Thu, Apr 9, 2026 at 7:26 PM Chao Li <li.evan.chao@gmail.com> wrote:
> 0001 and 0002 look good to me. I didn’t review 0003 and don’t intend to review it.

I've now pushed 0001 (34a3078629) and 0002 (d6e96bacd3c).

Here's the remaning patch to add src/test/modules/test_spi_resowner
rebased against master. I'm holding off on committing the test module
until I confirm the policy on new test modules during feature freeze.
It's also worth discussing whether this is the right place for testing
C extensions that use SPI with a dedicated resource owner, or whether
that coverage belongs elsewhere.

--
Thanks, Amit Langote

Attachment

pgsql-hackers by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: Re: Bug: WAIT FOR LSN crashes with assertion failure inside PL/pgSQL DO blocks and procedures
Next
From: Chao Li
Date:
Subject: Re: Add errdetail() with PID and UID about source of termination signal