Is it possible to fire triggers only on a read-only Postgres replicated database?
I want triggers to fire only on the replicated database - not on the master (to avoid load). This is to track - say - all updates/deletes.
Would enabling replica trigger be the way to go? On the primary/master, the triggers remain disabled, but in the replicated db, we can have the triggers fired?
The wal2json plugin is an option, but triggers seem a safer bet.