Re: pg_listener in 9.0 - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: pg_listener in 9.0
Date
Msg-id c3961794d12d9d49f68adbbfd73ce7bc@biglumber.com
Whole thread Raw
In response to pg_listener in 9.0  (Dave Page <dpage@pgadmin.org>)
Responses Re: pg_listener in 9.0
List pgsql-hackers
-----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. :)

- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201106010838
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk3mNEAACgkQvJuQZxSWSsh8LQCeKD/ot4mvXXd5Lgk4sIHwV0D2
CKsAn3Ub9Bdh0Fuyc0rDZr/OiSD8tkXq
=cdCn
-----END PGP SIGNATURE-----





pgsql-hackers by date:

Previous
From: panam
Date:
Subject: Re: [PERFORM] Hash Anti Join performance degradation
Next
From: Alexander Korotkov
Date:
Subject: Re: Cube Index Size