Re: system views for walsender activity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: system views for walsender activity
Date: 2010-06-18 14:21:52
Message-ID: 11965.1276870912@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Let's discuss what the best possible user interface for the information
> would be first, and then decide if we need/want to force an initdb for
> that. We have pg_upgrade now, that makes initdb less painful, and if
> it's just a new view it might be possible to just add a note in the
> release notes that you'll have to run the CREATE VIEW manually if upgrading.

The view would presumably depend on a C-language SRF, which isn't there
either.

I'm of the opinion that this is a 9.1 problem. It needs more thought
than we can put into it now --- one obvious question is what about
monitoring on the slave side? Another is who should be able to see the
data?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message depstein 2010-06-18 14:26:05 pg_upgrade issues
Previous Message Tom Lane 2010-06-18 13:59:57 Re: Debug message in RemoveOldXlogFiles