From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tomonari Katsumata <katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #7803: Replication Problem(no master is there) |
Date: | 2013-01-11 14:11:28 |
Message-ID: | CA+U5nM+T7UbzziULTx22sSQQqvXqJ-AVzzdqDn-q=4k94pu_Ew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Reiser | 2013-01-11 15:32:35 | Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
Previous Message | Dave Cramer | 2013-01-11 13:19:41 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |