Osmar
Osmar•2w ago

GitHub - ihippik/wal-listener: PostgreSQ...

Hey guys, is there a way to enable/send the old_row on postgresql trigger [update]? I want to check what has been updated on the code but right now it just sends the row already updated i saw that is possible like on https://github.com/ihippik/wal-listener but i dont know what to do, already put FULL on the replica identity
GitHub
GitHub - ihippik/wal-listener: PostgreSQL WAL listener
PostgreSQL WAL listener. Contribute to ihippik/wal-listener development by creating an account on GitHub.
4 Replies
Hugo
Hugo•7d ago
@dieriba_ would it be feasible?
dieriba_
dieriba_•7d ago
yes on it
Osmar
OsmarOP•7d ago
Let me jnow if i can help with anything here 🙂 Also noticed some possible unexpected behaviors: - When i remove the trigger it does not clean up pg_replication_slots; (After some time it will be full of unused slots) - Also it does not remove pg_publication from the db Steps to reproduce: Add a postgresql trigger check the db SELECT * FROM pg_replication_slots; SELECT * FROM pg_publication; Remove it The data will be still there
dieriba_
dieriba_•6d ago
We merged it, you now have access to the old_row argument which hold old data row if any. It is expected. when you delete a postgres trigger it does not automatically clear the associated resource instead a panel pops up, asking you if you want to delete the publication and/or replication slot associated to that trigger.

Did you find this page helpful?