3 ms·
A crucial facet of optimization for computational triggers in PostgreSQL pertains to the implementation of event triggers, which enable operations to be execute
by samanator 4y ago
A crucial facet of optimization for computational triggers in PostgreSQL pertains to the implementation of event triggers, which enable operations to be executed in bulk (per DML statement) rather than on a per-row basis. It appears that, at present, PL/Rust has not incorporated support for event triggers. According to the documentation:
> Event Triggers and DO blocks are not (yet) supported by PL/Rust.
- ttfkam 4y agoEvent triggers fire on DDL changes, not DML. You're thinking of statement-level triggers. As far as event triggers and DO-blocks, that omission seems fine to me. Especially DO-blocks, which are essentially an inline code, one-off escape hatch in the middle of other SQL. Rust would not be helping any performance-sensitive critical paths in those cases.
- doctor_eval 4y agoTrue, but it’s sometimes useful for experimenting, REPL style.
- samanator 4y agoYou're right! My mistake. I was thinking of statement triggers. https://www.postgresql.org/docs/current/sql-createtrigger.html https://www.postgresql.org/docs/current/sql-createtrigger.ht... > The REFERENCING option enables collection of transition relations I don't see any examples of statement triggers...
- ttfkam 4y agohttps://stackoverflow.com/a/72397774 https://stackoverflow.com/a/72397774 Note the use of new_table and old_table as aliases. Instead of single records in NEW and OLD, you can select against new and old sets of records.
- samanator 4y agoI understand, and I've used the old and new table aliases. But I meant that I don't see a way to use those in the PL/Rust docs.