I believe this fixes the bug because the failure was causing continuous failures to handle that notification which was grabbing lots of connections to the database.
It floods the logs on the attached bug. This is the only reason I can see him getting that strange error from postgresql.
I believe this fixes the bug because the failure was causing continuous failures to handle that notification which was grabbing lots of connections to the database.
It floods the logs on the attached bug. This is the only reason I can see him getting that strange error from postgresql.