Re: system views for walsender activity

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>, Josh Berkus <josh@agliodbs.com>, "Joshua D. Drake" <jd@commandprompt.com>, pgsql-hackers@postgresql.org
Date: 2011-01-04T19:56:55Z
Lists: pgsql-hackers
On 04.01.2011 21:43, Robert Haas wrote:
> On Tue, Jan 4, 2011 at 2:31 PM, Magnus Hagander<magnus@hagander.net>  wrote:
>> On Tue, Jan 4, 2011 at 20:28, Josh Berkus<josh@agliodbs.com>  wrote:
>>>
>>>> hmmm I think "pg_stat_standby" might be more relevant but I definitely
>>>> agree something more newbie appropriate is in order.
>>>
>>> I'd be fine with that name, too.
>>
>> That seems kind of backwards though - given that the view only
>> contains data on the master...
>
> I think pg_stat_replication is better than pg_stat_standby, but I'm
> still not convinced we shouldn't go with the obvious
> pg_stat_walsenders.

How about pg_stat_replication_activity? If I understood correctly, the 
view is similar to pg_stat_activity, but displays information about 
connected standbys rather than regular backends. It's a bit long name, 
though.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com