Skip site navigation (1) Skip section navigation (2)

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: petteri(dot)raty(at)aalto(dot)fi
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6619: Misleading output from slave when host is not running
Date: 2012-04-27 18:29:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Fri, Apr 27, 2012 at 3:47 AM,  <petteri(dot)raty(at)aalto(dot)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
The Enterprise PostgreSQL Company

In response to

pgsql-bugs by date

Next:From: Jeff FrostDate: 2012-04-27 18:54:34
Subject: Re: 9.1.3 backends getting stuck in 'startup'
Previous:From: Robert HaasDate: 2012-04-27 18:24:53

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group