Re: BUG #7803: Replication Problem(no master is there) - Mailing list pgsql-bugs

From Tomonari Katsumata
Subject Re: BUG #7803: Replication Problem(no master is there)
Date
Msg-id 50F4E52E.9000603@po.ntts.co.jp
Whole thread Raw
In response to Re: BUG #7803: Replication Problem(no master is there)  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: BUG #7803: Replication Problem(no master is there)
List pgsql-bugs
Hi,

Sorry for late response.

(2013/01/11 23:11), Simon Riggs wrote:
 > On 11 January 2013 12:18, Tomonari Katsumata
 > <katsumata.tomonari@po.ntts.co.jp> wrote:
 >
 >> I'm not sure but what about adding the parameter("cascade_mode") on
 >> recovery.conf ?
 >> The parameter represents a will to connect to standby server when
starting
 >> as standby.
 >> If the parameter is set to on, connect to a server forcely like
PostgreSQL
 >> 9.2,
 >> and if the parameter is set to off, connect to the another standby
server is
 >> refused like PostgreSQL 9.1.
 >
 > We added a REPLICATION privelge onto user accounts to control access.
 >
 > Perhaps we should add a CASCADE privilege as well, so that we can
 > control whether we can connect to a master and/or a standby.
 >
 > Syntax would be
 >
 > ALTER USER foo
 > [MASTER | CASCADE] REPLICATION
 >
 > REPLICATION allows both master and cascaded replication (same as now)
 > MASTER REPLICATION allows master only
 > CASCADE REPLICATION allows cascaded replication only
 > NOREPLICATION allows neither option
 >

This idea seems better than mine.

Someone is working for it already ?
If not yet, may I try to implement it ?

regards,
--------
NTT Software Corporation
  Tomonari Katsumata

pgsql-bugs by date:

Previous
From: richardbrown360@hotmail.com
Date:
Subject: BUG #7810: cant uninstall or install program
Next
From: Simon Riggs
Date:
Subject: Re: BUG #7803: Replication Problem(no master is there)