From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_listener in 9.0 |
Date: | 2011-06-01 13:27:27 |
Message-ID: | BANLkTi=LX+J=zaHMkr4NxVx0OWptCZDAEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 1, 2011 at 12:45 PM, Greg Sabino Mullane <greg(at)turnstep(dot)com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>> 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?
>
> Nope, you are out of luck: the information is locked away and cannot
> be seen by other processes. I'm sure of this because Bucardo
> went through the same questioning some time ago. We basically rewrote
> the app a bit to use the on-disk PID files to replace some of the
> lost functionality, and sucked up the rest. :)
:-(
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2011-06-01 13:30:48 | Re: pg_listener in 9.0 |
Previous Message | Alexander Korotkov | 2011-06-01 13:05:03 | Re: Cube Index Size |