|
Hi.
After applying the latest patch we have encountered a problem
with the pg_notify queue.
The queue is filling up and starts issuing warnings like
WARNING: NOTIFY queue is 87% full
DETAIL: The server process with PID 2969993 is among those
with the oldest transactions.
NOTIFY queue cannot be emptied until that process ends its current
transaction.
There is no long-running 'active' or 'idle in transaction' transactions
on the server.
We restarted the application with the said pid but the result was
that the new process pid appeared in the logs instead.
We tried to stop
everything except postgresql it self but the queue was not purged. After restarting postgresql the queue is empty and seems to be holding up for an hour or so before it starts growing again.
We have been using pg_notify / listen for about three years and haven’t run in to this problem
before so it seems to me that something happened in the latest patch.
PG version: 11.10
with slony. The notify triggers is on the master node.
KR.
Mikael Gustavsson
SMHI
Swedish
Meteorological and Hydrological Institute
|
