Re: [PostgreSQL 10] default of hot_standby should be "on"?

From: Vaishnavi Prabakaran <vaishnaviprabakaran(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Huong Dangminh <huo-dangminh(at)ys(dot)jp(dot)nec(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Hiroshi Yanagisawa <hir-yanagisawa(at)ut(dot)jp(dot)nec(dot)com>
Subject: Re: [PostgreSQL 10] default of hot_standby should be "on"?
Date: 2017-04-27 00:42:19
Message-ID: CAOoUkxQLiEP7G+ceFCyLEkOZaMoavu-YisXUqZVzm4Z-avM+hQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 26, 2017 at 9:52 PM, Magnus Hagander <magnus(at)hagander(dot)net>
wrote:

>
> 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.
>
> Perhaps, you mean hot_standby=off here?

Regards,
Vaishnavi
Fujitsu Australia.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Huong Dangminh 2017-04-27 00:54:19 Re: [PostgreSQL 10] default of hot_standby should be "on"?
Previous Message Andres Freund 2017-04-27 00:37:40 Re: Unportable implementation of background worker start