| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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 11:27:09 |
| Message-ID: | 4DE6220D.1020903@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01.06.2011 13:09, Dave Page 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?
Hmm, my first thought was that we should add a view to display that
information, but that's not possible, because we don't have that
information in shared memory. The information on what channels are being
listened on is now backend-local.
Does the slon process set application_name? You could query
pg_stat_activity with that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-06-01 11:37:41 | Re: Cube Index Size |
| Previous Message | Greg Smith | 2011-06-01 10:09:56 | Re: Getting a bug tracker for the Postgres project |