| 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:13:55 |
| Message-ID: | 56C73133.6030508@aklaver.com |
| Views: | Whole Thread | Raw Message | 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.
Well from here:
"There is one central queue in disk-based storage (directory pg_notify/),
with actively-used pages mapped into shared memory by the slru.c module.
All notification messages are placed in the queue and later read out
by listening backends."
and from here:
http://www.postgresql.org/docs/9.5/interactive/sql-notify.html
"The queue is quite large (8GB in a standard installation) ..."
I could see setting up file monitoring in pg_notify/ of the queue file size.
>
> Thanks,
> Jiri
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2016-02-19 15:21:02 | Re: Monitoring and insight into NOTIFY queue |
| Previous Message | Merlin Moncure | 2016-02-19 15:08:01 | Re: Monitoring and insight into NOTIFY queue |