Re: NOTIFY queue is at 66% and climbing... - Mailing list pgsql-general

From Tom Lane
Subject Re: NOTIFY queue is at 66% and climbing...
Date
Msg-id 712282.1634169057@sss.pgh.pa.us
Whole thread Raw
In response to NOTIFY queue is at 66% and climbing...  (Jeff Ross <jross@openvistas.net>)
Responses Re: NOTIFY queue is at 66% and climbing...
List pgsql-general
Jeff Ross <jross@openvistas.net> writes:
> On 10.15 I'm getting the following on a logically replicated server.

> 2021-10-13 18:49:39.792 EDT,,,213601,,6143c257.34261,64243,,2021-09-16 
> 18:16:55 EDT,4/3914851,60709901,WARNING,01000,"NOTIFY queue is 66% 
> full",,,,,,,,,""

> In the CSV logs above what part points to "the session that is 
> preventing cleanup" so that I can kill it?

Normally there's a DETAIL entry citing the session's PID.  Looking
at the code, the reason for the lack of any such entry must be that
there is no session whose current notify queue position exactly
matches the supposed global minimum position.  This corresponds to
a known bug that was fixed in 10.16, so I'd suggest upgrading.
As a temporary workaround you could restart that server, but
likely the problem would recur after awhile.

            regards, tom lane



pgsql-general by date:

Previous
From: "Phil Endecott"
Date:
Subject: Re: Replication between different architectures
Next
From: Eric Tobias
Date:
Subject: RE: Duplicate key in UUID primary key index...