On Wed, Oct 3, 2012 at 6:41 AM, Gabriele Bartolini <Gabriele.Bartolini@xxxxxxxxxxxxxx> wrote: > Hi Greg, > > > On Tue, 2 Oct 2012 15:02:23 -0700 (PDT), Greg Williamson > <gwilliamson39@xxxxxxxxx> wrote: > >> Other than abandoning repmgr I don't see a solution. I've posted this >> to the repmgr discussion group but have had zero responses (and, >> frankly, am not holding my breath). > > > If you are 100% sure it is repmgr ... :) > > I am not 100% sure it is ... Under normal circumstances (once the standby > has been cloned), repmgr simply controls the status of a standby server > communicating with a master through the streaming replication protocol. As > any other standby would do. > more to the point... if this is happening on master (where you can create and drop databases), then repmgrd has no reason to be running there... and very limited subset of commands (master register, cluster show, cluster cleanup) can be run on master -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
