3 ms·
Be aware that Postgres' NOTIFY is not stored/queued in any way. If your external client is not listening, it will get lost. I would instead have the trigger in
by gnud 10y ago
Be aware that Postgres' NOTIFY is not stored/queued in any way. If your external client is not listening, it will get lost.
I would instead have the trigger insert a row into a "pending tasks" table - and then send a NOTIFY.
- lima 10y agohttp://debezium.io/ http://debezium.io/ is a better way to do this. It uses the logical decoding feature to get all row changes and writes them to a Kafka queue. This means it can pick up where it left when it crashes.
- ruslan_talpa 10y agoalong the same lines https://github.com/confluentinc/bottledwater-pg https://github.com/confluentinc/bottledwater-pg