Re: system views for walsender activity

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: system views for walsender activity
Date: 2010-06-22 11:29:19
Message-ID: 4C209E8F.4050605@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le 22/06/2010 12:42, Simon Riggs a écrit :
> On Tue, 2010-06-22 at 12:19 +0200, Guillaume Lelarge wrote:
>> Shamely simple : I only added some informations on the server's
>> properties. See
>> http://www.pgadmin.org/images/visualtour12/visualtour08.jpg. We only
>> display the fact that the server is (or isn't) in recovery, and the
>> result of the two admin functions (receive and replay location).
>
> If you store the is-in-Recovery result you could set the .enabled
> property of many of the dialog boxes. I think its going to be painful
> for people to attempt to submit a DDL command and get an error.
>

That's what I first thought. But it would be weird that we disabled all
the OK button of the dialog properties only for hotstandby servers, but
not when a user doesn't have the permission. At least, that was the
reasonning I had at the time.

>> Too bad the other admin functions aren't there, I could have used them
>> (and hope to do so in 9.1). Too bad also we cannot know the primary
>> server from a connection to the slave (that's why I would love to get
>> the value of
>> primary_conninfo, to found the alias/IP of the primary server).
>
> Agreed
>

:)

--
Guillaume
http://www.postgresql.fr
http://dalibo.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-06-22 13:20:39 Re: TCP keepalive support for libpq
Previous Message Simon Riggs 2010-06-22 10:42:01 Re: system views for walsender activity