Thanks all for your comments. > Magnus Hagander <mag...@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/
hot_standby.patch
Description: hot_standby.patch
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers