From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_listener in 9.0 |
Date: | 2011-06-01 13:55:45 |
Message-ID: | BANLkTimHiQh7WHZSHX7KecFpzP_76_c6bQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 1, 2011 at 5:09 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> The pg_listener table was removed in 9.0 in the revamp of
> LISTEN/NOTIFY. In pgAdmin we used to perform a number of selects from
> the table to get information about Slony clusters - for example, the
> PID of the slon process or to check if a process is listening for a
> specific notification. This allows the app to indicate to the user if
> there is something wrong with their replication cluster.
>
> I can't find any way to get that information now - any ideas?
Although it might not be helpful in your case, you can emulate certain
aspects of this with an advisory lock...you can query the lock table
for specific locks, and it goes away when the connection dies.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Singer | 2011-06-01 14:02:19 | Re: pg_listener in 9.0 |
Previous Message | Christopher Browne | 2011-06-01 13:30:48 | Re: pg_listener in 9.0 |