"
2) notify does not work with pgbouncer (yet), although I have in the
past had a private pgbouncer with functioning notify."
Is there a plan to make it work?
Actually - stupid question - probably not important... But good to know...
Listen connection doesn't need to work via pgbouncer...
Thanks,
Misa
On Friday, April 26, 2013, Merlin Moncure wrote:
On Fri, Apr 26, 2013 at 11:30 AM, Perry Smith <pedzsan@gmail.com> wrote:
> Hi,
>
> I'm curious what the design assumptions of the LISTEN / NOTIFY are. For example, would it work to have a thousand LISTEN channels open at the same time or would that be abusing the assumptions that were made? In short, I'm trying to understand if I need a few central LISTEN / NOTIFY channels that then distribute the events out or not.
Couple quick points about notify:
1) In somewhat recent postgres (9.0) notify implementation was
significantly optimized and expanded to include a payload.
2) notify does not work with pgbouncer (yet), although I have in the
past had a private pgbouncer with functioning notify.
3) notifies are not delivered until end of transaction, which is
sometimes useful, sometimes annoying
4) delivery of notifications is 'best effort', but that effort is
pretty much always successful.
5) listener's in the range of 1000's is ok. but don't be afraid to
think about using payload and/or putting specific instructions into a
table that the client listener acts on after receiving notify.
merlin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
