modify: request for new parameter for disable promote (slave onlymode) - Mailing list pgsql-hackers

From Ioseph Kim
Subject modify: request for new parameter for disable promote (slave onlymode)
Date
Msg-id 20180728145636.deb6k6wonwsirqfh@postgresql.kr
Whole thread Raw
In response to request for new parameter for disable promote (slave only mode)  (Ioseph Kim <pgsql-kr@postgresql.kr>)
List 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’svalues.
 
> 
> 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. 
> 
> 


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: pgbench - add pseudo-random permutation function
Next
From: Tom Lane
Date:
Subject: Re: Removing useless \. at the end of copy in pgbench