Re: BUG #7803: Replication Problem(no master is there)

From: Tomonari Katsumata <katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7803: Replication Problem(no master is there)
Date: 2013-01-15 05:12:14
Message-ID: 50F4E52E.9000603@po.ntts.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

Sorry for late response.

(2013/01/11 23:11), Simon Riggs wrote:
> On 11 January 2013 12:18, Tomonari Katsumata
> <katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Simon Riggs 2013-01-15 08:14:09 Re: BUG #7803: Replication Problem(no master is there)
Previous Message richardbrown360 2013-01-15 00:22:36 BUG #7810: cant uninstall or install program