Kevin Grittner wrote: > Bruce Momjian <br...@momjian.us> wrote: > > > One odd thing is we have two paramters that mention hot_standby > > --- on the master we have to do in postgresql.conf: > > > > wal_level = hot_standby > > > > and on the slave we do in postgresql.conf: > > > > hot_standby = on > > > > That is a little confusing. > > Why? I read that as saying that the master is writing sufficient > data into the WAL for it to be usable for hot standby purposes, and > that that the slave machine is going to be used as a hot standby. > You'd better do the former if you're going to do the latter, but > there were good reasons not to try to infer one setting from the > other.
My point was that the string 'hot_standby' is both a variable and a setting. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
