We're in the process of converting our triggers from a custom
framework where they ran in Java just above the database into native
PostgreSQL triggers. We've run into an issue in testing, and I
think I see a workable solution. It seems like a bit of a hack, but
it looks like it will work, and I
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
To emulate this logic in a PostgreSQL trigger, I think I can define
a security definer trigger function created by the database
superuser with session_replication_mode set for the function to
'replica'. It's a lie, but it seems like it
