On Fri, Apr 27, 2012 at 3:47 AM, <petteri.r...@aalto.fi> wrote: > When I started the slave without the master running I got the following > output: > > $ postgres -D gsd-replica/ > LOG: database system was interrupted while in recovery at log time > 2012-04-25 12:01:33 UTC > HINT: If this has occurred more than once some data might be corrupted and > you might need to choose an earlier recovery target. > LOG: entering standby mode > WARNING: WAL was generated with wal_level=minimal, data may be missing > HINT: This happens if you temporarily set wal_level=minimal without taking > a new base backup. > FATAL: hot standby is not possible because wal_level was not set to > "hot_standby" on the master server > HINT: Either set wal_level to "hot_standby" on the master, or turn off > hot_standby here. > LOG: startup process (PID 28761) exited with exit code 1 > LOG: aborting startup due to startup process failure > > The error message above on the FATAL line is wrong (or at least misleading).
I think it's trying to tell you that you had wal_level=minimal configured on the master *at the time you took the base backup*. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
