Re: event trigger support for PL/Python
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Euler Taveira <euler@eulerto.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-08-08T05:04:34Z
Lists: pgsql-hackers
pá 8. 8. 2025 v 1:31 odesílatel Euler Taveira <euler@eulerto.com> napsal: > 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 ok Regards Pavel > > > > -- > Euler Taveira > EDB https://www.enterprisedb.com/ >
Commits
-
PL/Python: Add event trigger support
- 53eff471c69d 19 (unreleased) landed
-
PL/Python: Refactor for event trigger support
- 6e09c960ebb3 19 (unreleased) landed