Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"? - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?
Date
Msg-id CAD21AoDvtF0z3LWxC5CWAZA+2dgGe3YCOPCso5SXX=-T64hy5g@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
List pgsql-hackers
On Wed, Apr 26, 2017 at 9:36 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> On 26 April 2017 at 08:30, Huong Dangminh <huo-dangminh@ys.jp.nec.com> wrote:
>
>> Default for hot_standby parameter should be "on" from PostgreSQL 10?
>>
>> In PostgreSQL 10, -w option is default for [pg_ctl start].
>> So in order to start standby we have to setting hot_standby to "on" or
>> start standby with -W option.
>
> Yeah. That's a good reason to change it. I think at this point warm
> standby is clearly the less-used secondary option and hot_standby
> should be default.
>

The idea of changing the default value seems good to me but I'm not
sure it's good idea to change the default value now under the
circumstances where we're focus on stabilization.
Also we should update the document as well.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] subscription worker doesn't start immediately oneabled
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?