Re: [GENERAL] NOTIFY command impact - Mailing list pgsql-general

From David G. Johnston
Subject Re: [GENERAL] NOTIFY command impact
Date
Msg-id CAKFQuwb=tsEG9UT+pvhgmqYjSuvKTgkbFo+co2KsQ8t-qKaJQw@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] NOTIFY command impact  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: [GENERAL] NOTIFY command impact  (Rob Brucks <rob.brucks@rackspace.com>)
List pgsql-general
On Tue, Feb 21, 2017 at 2:17 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 02/21/2017 01:07 PM, Rob Brucks wrote:

Do you see any long-term problems with constantly issuing "NOTIFY"
commands every 30 seconds without an associated "LISTEN" command?

Depending on how long 'long term' is:

https://www.postgresql.org/docs/9.6/static/sql-notify.html

"There is a queue that holds notifications that have been sent but not yet processed by all listening sessions

​Its not clear in the OP that this is the case (it seems to be) but the documentation is non-specific as to what happens when "# of listeners" = 0;  I suspect that said messages are created and then immediately discarded - though apparently they do make it over to the standby server​ too - and likely also immediately discarded there as well.

David J.

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: [GENERAL] Wired-Protocol Specification?
Next
From: Patrick B
Date:
Subject: [GENERAL] bloat indexes - opinion