Re: BUG #6619: Misleading output from slave when host is not running

On Fri, Apr 27, 2012 at 3:47 AM,  <petteri.raty@aalto.fi> wrote:
> When I started the slave without the master running I got the following
> output:
>
> $ postgres -D gsd-replica/
> LOG: =A0database system was interrupted while in recovery at log time
> 2012-04-25 12:01:33 UTC
> HINT: =A0If this has occurred more than once some data might be corrupted=
 and
> you might need to choose an earlier recovery target.
> LOG: =A0entering standby mode
> WARNING: =A0WAL was generated with wal_level=3Dminimal, data may be missi=
ng
> HINT: =A0This happens if you temporarily set wal_level=3Dminimal without =
taking
> a new base backup.
> FATAL: =A0hot standby is not possible because wal_level was not set to
> "hot_standby" on the master server
> HINT: =A0Either set wal_level to "hot_standby" on the master, or turn off
> hot_standby here.
> LOG: =A0startup process (PID 28761) exited with exit code 1
> LOG: =A0aborting startup due to startup process failure
>
> The error message above on the FATAL line is wrong (or at least misleadin=
g).

I think it's trying to tell you that you had wal_level=3Dminimal
configured on the master *at the time you took the base backup*.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company