On Mon, Mar 24, 2014 at 8:59 PM, Fujii Masao wrote:
> On Sat, Mar 22, 2014 at 9:33 AM, Tatsuo Ishii wrote:
>>> That's because the parameter is checked at the beginning of recovery
>>> (i.e. at standby start) before XLOG_PARAMETER_CHANGE is received and
>>> applied on the standby. Please see Chec
On Sat, Mar 22, 2014 at 9:33 AM, Tatsuo Ishii wrote:
>> That's because the parameter is checked at the beginning of recovery
>> (i.e. at standby start) before XLOG_PARAMETER_CHANGE is received and
>> applied on the standby. Please see CheckRequiredParameterValues() in
>> StartupXLOG().
>>
>> To p
> That's because the parameter is checked at the beginning of recovery
> (i.e. at standby start) before XLOG_PARAMETER_CHANGE is received and
> applied on the standby. Please see CheckRequiredParameterValues() in
> StartupXLOG().
>
> To persist the max_connections change:
>
> 1) stop primary
> 2
From: "Tatsuo Ishii"
Last time I tested in following way, max_connections in pg_control of
standby did not reflect the change in primary.
1) stop primary
2) stop standby
3) change max_connections to 4 in primary
4) change max_connections to 4 in standby
5) start primary
6) start standby but it
> The primary log the new value as an XLOG_PARAMETER_CHANGE WAL record
> at startup when the parameter value in postgresql.conf does not match
> the one in pg_control. Then, the WAL record is sent to the standby
> and applied, which changes the value in pg_control on the standby.
Last time I test
From: "Rajeev rastogi"
If you changed max_connection to 4 only in primary, then I am not able to
understand, how it got changed in standby also (if you have not taken back
again)?
Let me know If I have missed something.
The primary log the new value as an XLOG_PARAMETER_CHANGE WAL record at
On 21 March 2014 16:17, Tatsuo Wrote:
> In my case I had already changed primary's max_connections to 4 and
> restarted it. So at that point both postgresql.conf of primary and
> standby were 4.
If you changed max_connection to 4 only in primary, then I am not able to
understand, how it got cha
>> I changed primary servers max_connections from 100 to 4 for just a
>> testing purpose. Now standby server won't start and complains:
>>
>> hot standby is not possible because max_connections = 4 is a lower
>> setting than on the master server (its value was 100)
>>
>> My guess is this is becau
On 21 March 2014 13:41, Tatsuo Wrote:
> I changed primary servers max_connections from 100 to 4 for just a
> testing purpose. Now standby server won't start and complains:
>
> hot standby is not possible because max_connections = 4 is a lower
> setting than on the master server (its value was 10
