From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Jiří Hlinka <jiri(dot)hlinka(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Monitoring and insight into NOTIFY queue |
Date: | 2016-02-19 15:21:02 |
Message-ID: | 56C732DE.5090509@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/19/2016 06:01 AM, Jiří Hlinka wrote:
> Hello,
>
> I'd like to ask you whether there is a way how to monitor and log
> details about NOTIFY queue? What do you use for this prupose?
>
> In the official documentation I'm unable to find a way how to monitor
> NOTIFY queue in more detail, at least size of this queue, which is
> critical in case of filling up the queue, which will lead to stopping
> the NOTIFY queue functionality.
Should have added from:
http://www.postgresql.org/docs/9.5/interactive/sql-notify.html
"Once the queue is half full you will see warnings in the log file
pointing you to the session that is preventing cleanup. In this case you
should make sure that this session ends its current transaction so that
cleanup can proceed"
Where the message is of form(from async.c):
(errmsg("NOTIFY queue is %.0f%% full", fillDegree * 100),
(minPid != InvalidPid ?
errdetail("The server process with
PID %d is among those with the oldest transactions.", minPid)
: 0),
(minPid != InvalidPid ?
errhint("The NOTIFY queue cannot be
emptied until that process ends its current transaction.")
: 0)));
>
> Thanks,
> Jiri
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Don Parris | 2016-02-19 16:12:28 | Re: Charlotte Postgres User Group |
Previous Message | Adrian Klaver | 2016-02-19 15:13:55 | Re: Monitoring and insight into NOTIFY queue |