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

From Huong Dangminh
Subject Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?
Date
Msg-id 75DB81BEEA95B445AE6D576A0A5C9E936A625785@BPXM05GP.gisp.nec.co.jp
Whole thread Raw
In response to Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Thanks all for your comments.

> Magnus Hagander <magnus@hagander.net> writes:
> > +1. I definitely think we should do it, and 10 would be the time to do
> it.
>
> Agreed.  It's mainly a historical accident that the default is what it
> is,
> I think.
>
> > I wonder if we should also consider changing the standby error message
> to
> > be a WARNING instead of an ERROR. So that if you try to start up a standby
> > with hot_standby=on but master with wal_level=replica it would turn into
> a
> > cold standby.
>
> I'm -1 for that: if you fat-finger the configuration, you should be told
> about it, not have the system start up in an unintended mode that lacks
> critical functionality.
>
>             regards, tom lane

I attached the patch which also update manual as the mention of sawada-san.

---
Thanks and best regards,
Dang Minh Huong
NEC Solution Innovators, Ltd.
http://www.nec-solutioninnovators.co.jp/en/

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Vaishnavi Prabakaran
Date:
Subject: Re: [HACKERS] [PostgreSQL 10] default of hot_standby should be "on"?
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Unportable implementation of background worker start