| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: event trigger clarification |
| Date: | 2023-08-30 18:44:49 |
| Message-ID: | CAKFQuwasdmAKC3J=gGf5LSZ7oh8KbCu_XGWKqeh0O=p9a2X_UQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday, August 30, 2023, Marc Millas <marc(dot)millas(at)mokadb(dot)com> wrote:
> Hi,
> the doc v15 states: " pg_event_trigger_ddl_commands returns a list of DDL commands
> executed by each user action, when invoked in a function attached to a
> ddl_command_end event trigger."
> When some ddl command is executed within a block, I would like to know if
> the event trigger fires when the line is executed or at commit time.
>
https://www.postgresql.org/docs/current/event-trigger-definition.html
There is nothing there about event execution being able to be deferred.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitrios Apostolou | 2023-08-30 19:55:01 | Partitionwise JOIN scanning all partitions, even unneeded ones |
| Previous Message | Erik Wienhold | 2023-08-30 16:18:51 | Re: event trigger clarification |