Re: event trigger support for PL/Python

Euler Taveira <euler@eulerto.com>

From: "Euler Taveira" <euler@eulerto.com>
To: "Pavel Stehule" <pavel.stehule@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-08-07T23:31:18Z
Lists: pgsql-hackers
On Thu, Aug 7, 2025, at 1:53 AM, Pavel Stehule wrote:
> Minimally - you should to use PLPY_DML_TRIGGER instead PLPY_TRIGGER
>

I didn't use DML terminology for the same reason Peter said in another thread
[1]; let's *not* introduce a new terminology (DML trigger).

> Maybe the name "trigtype" can be better than "is_trigger". The 
> similarity with PLpgSQL has some benefits, but in this case I think so 
> the plpgsql design (of this case) is minimally confusing (and really 
> the related part in plpgsql_compile_callback can be cleaned). How much 
> - this is a question. There are two different things that are mixed 
> together (and this is what I dislike):
>

I'm fine with trigger kind or trigger type but I wouldn't like to use DML
trigger.


[1] https://www.postgresql.org/message-id/1379995202.8103.4.camel@vanquo.pezone.net


-- 
Euler Taveira
EDB   https://www.enterprisedb.com/



Commits

  1. PL/Python: Add event trigger support

  2. PL/Python: Refactor for event trigger support