modify: request for new parameter for disable promote (slave only mode)

From: Ioseph Kim <pgsql-kr(at)postgresql(dot)kr>
To: pgsql-hackers(at)postgresql(dot)org
Subject: modify: request for new parameter for disable promote (slave only mode)
Date: 2018-07-28 14:56:36
Message-ID: 20180728145636.deb6k6wonwsirqfh@postgresql.kr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sorry, I was misstyped.

non shared -> shared

On Sat, Jul 28, 2018 at 01:05:40AM +0900, Ioseph Kim wrote:
> Hi.
>
> I want to build one master & multi slave environments to use physical replication.
> Slave nodes have low hardware spec, so I changed max_connection server parameters, and try start slave node.
> But I could not start slave nodes,
> because CheckRequiredParameterValues function (in src/backend/access/transam/xlog.c) reject to set less values then master’s values.
>
> It is maybe,
> This concept is base on some slave node can be promte master.
> In my enterprise environments, readonly slave nodes are not used as master.
> For High availability of master node, I’m using non shared disk fail over (like using pacemaker),
> Then my slave nodes are used for always readonly nodes.
>
> I suggest that new server parameter is added, such like allow_promote = on|off.
> If allow_promte set off then CheckRequiredParameterValues skip check slave node parameters.
>
> If there is a better plan, it is welcome too.
>
> Regards, ioseph.
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-07-28 15:10:54 Re: Removing useless \. at the end of copy in pgbench
Previous Message Fabien COELHO 2018-07-28 14:03:49 pgbench - add pseudo-random permutation function