Re: system views for walsender activity
Guillaume Lelarge <guillaume@lelarge.info>
From: Guillaume Lelarge <guillaume@lelarge.info>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>, Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2010-06-22T11:29:19Z
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