| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Gustavsson Mikael <mikael(dot)gustavsson(at)smhi(dot)se> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Svensson Peter <peter(dot)svensson(at)smhi(dot)se>, Almen Anders <anders(dot)almen(at)smhi(dot)se> |
| Subject: | Re: Problem with pg_notify / listen |
| Date: | 2020-11-27 14:28:10 |
| Message-ID: | CAKFQuwb9rYE0FkBrg67at70VnX3kT+h7_SWxtRnJ8=Bvw7wDPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
On Friday, November 27, 2020, Gustavsson Mikael <mikael(dot)gustavsson(at)smhi(dot)se>
wrote:
> 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.
>
>
As its easy enough to run can you please confirm this by showing us the
pg_stat_activity record for that pid during the time when this warning
appears?
Thanks!
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gustavsson Mikael | 2020-11-27 14:48:28 | SV: Problem with pg_notify / listen |
| Previous Message | Gustavsson Mikael | 2020-11-27 12:56:53 | Problem with pg_notify / listen |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zwettler Markus (OIZ) | 2020-11-27 14:36:28 | AW: How to debug authentication issues in Postgres |
| Previous Message | Gustavsson Mikael | 2020-11-27 12:56:53 | Problem with pg_notify / listen |