-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
listen/notify support with transaction pooling #85
Comments
It looks that right now listen notify requests open new connections and eventually overflow the system. Is there a work around? |
+1. can confirm that listen notify also overflows the system. |
What do you all mean "overflow the system"? Since listen requires a connection per Don't listen to more topics than your pool_size and make sure to use |
If I remember correctly it was something on my side. Either wrong mode or just too many listeners due to falsy settings on the client side. not an issue for me anymore. |
Inspired by allas
Use a single connection to proxy listen notify requests to all clients.
The text was updated successfully, but these errors were encountered: