3 ms·
The last time we did this, we basically hand-rolled our own, with a database trigger to insert data into a different table whenever an `UPDATE` statement happen
by pavel_lishin 2y ago
The last time we did this, we basically hand-rolled our own, with a database trigger to insert data into a different table whenever an `UPDATE` statement happened.
But this seems like it's probably a better solution.
- tough 2y agonever had used pgaudit yet to vouch for it but have it on the backburner/log of things to try for such a use case! I think the real magic is it lleverages the WAL (write ahead logs) from pg engine itself, which you could certainly hook up into too, but im not a db expert here
- tough 2y agoI just found out about bemi dot io, seems like they're targeting this issue