Realtime Postgres changes trigger multiple times
The docs show an example for how to set up different callbacks for different tables when setting up realtime postgres events with the Python client.
But when changes come in, it actually triggers the callback for the right table multiple times, one time for each other handler that was registered on the channel. So in this example with two handlers, any update on the
Any ideas on how to prevent this or why that could be the case?
But when changes come in, it actually triggers the callback for the right table multiple times, one time for each other handler that was registered on the channel. So in this example with two handlers, any update on the
messagesAny ideas on how to prevent this or why that could be the case?
