fazool mein <fazoolmein@xxxxxxxxx> writes: > I'm trying to test streaming replication. I set up a primary and secondary. > The primary starts normal, but when I start the standby, it doesn't start > up. The log looks like this: > LOG: database system was interrupted while in recovery at log time > 2010-08-23 13:30:43 EDT > 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 5875) exited with exit code 1 > LOG: aborting startup due to startup process failure > Note that I have checked multiple times that 'wal_level' is set to > 'hot_standby' on the primary, You need to do that *before* taking your base backup. The WARNING above indicates that the backup was taken with an inadequate wal_level setting. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
