2012/11/30 Igor Neyman iney...@perceptron.com
-Original Message-
From: Greg Sabino Mullane [mailto:g...@turnstep.com]
Sent: Thursday, November 29, 2012 11:34 PM
To: pgsql-general@postgresql.org
Subject: Re: pg_listening_channels()
On the contrary, it was very well
-Original Message-
From: Greg Sabino Mullane [mailto:g...@turnstep.com]
Sent: Thursday, November 29, 2012 11:34 PM
To: pgsql-general@postgresql.org
Subject: Re: pg_listening_channels()
On the contrary, it was very well discussed and designed. Why do you
even care if the anyone
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, November 28, 2012 6:13 PM
To: Igor Neyman
Cc: Greg Sabino Mullane; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_listening_channels()
Igor Neyman iney...@perceptron.com writes:
With PG 9.0
Igor Neyman iney...@perceptron.com writes:
[ shrug... ] It was debated extensively and the advantages of the new
implementation were deemed to outweigh the disadvantages.
Are you saying that these two features: attached payload and being able to
find which channels are being listened to -
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Igor Neyman wrote:
But, I (and probably many others) use LISTEN/NOTIFY mechanism to notify
client program connected to postgres database about changes made in the
database
Yes, it is commonly used for that.
Implementation prior to PG
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Igor Neyman asked:
[Postgres 9.2]
How (if it's even possible) can I get listening channels
for all sessions/ connections in the database?
No, this is not possible. You can only see items
from your own session.
- --
Greg Sabino Mullane
From: Greg Sabino Mullane [g...@turnstep.com]
Sent: Wednesday, November 28, 2012 10:26 AM
To: pgsql-general@postgresql.org
Subject: Re: pg_listening_channels()
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Igor Neyman asked:
[Postgres 9.2]
How
Igor Neyman iney...@perceptron.com writes:
With PG 9.0 changes I lost ability to check if anyone is interested in the
NOTIFY signal and payload I'm about to send.
Seems like this change was not thought through completely.
[ shrug... ] It was debated extensively and the advantages of the new
Hello,
In Postgresql 9.2 this function pg_listening_channels() returns the channels
that the current session/connection listens to.
How (if it's even possible) can I get listening channels for all sessions/
connections in the database?
With older versions I could just query pg_listener WHERE
