Re: BUG #6653: Service does not start in standby-mode

On Mon, May 21, 2012 at 6:45 AM,  <axw-sk@ipa.fhg.de> wrote:
> The following bug has been logged on the website:
>
> Bug reference: =A0 =A0 =A06653
> Logged by: =A0 =A0 =A0 =A0 =A0Sebastian K.
> Email address: =A0 =A0 =A0axw-sk@ipa.fhg.de
> PostgreSQL version: 9.0.7
> Operating system: =A0 Windows 7 i386
> Description:
>
> I want to set up a standby server for backup.
>
> The server has a new installation of postgresql.
>
> recovery.conf:
> restore_command =3D 'copy "c:\\Users\\Administrator\\Desktop\\%f" "%p"'
> standby_mode =3D 'on'
>
> The files of the base backup are placed on the Desktop of the standby
> server.
>
> Additionally, the files are already copied to the pg_xlog directory.
>
> Problem:
> Placing the recovery.conf file in the data directory prevents the postgres
> service to start.
>
> Windows-Error-Log:
> Starting service timeout.
>
> PG-Log:
> 2012-05-21 12:38:38 CEST LOG: =A0Datenbanksystem wurde w=E4hrend der
> Wiederherstellung am 2012-05-21 12:34:21 CEST heruntergefahren
> 2012-05-21 12:38:38 CEST LOG: =A0Standby-Modus eingeschaltet
> 2012-05-21 12:38:38 CEST FATAL: =A0das Datenbanksystem startet
> 2012-05-21 12:38:38 CEST WARNUNG: =A0WAL wurde mit wal_level=3Dminimal er=
zeugt,
> eventuell fehlen Daten
> 2012-05-21 12:38:38 CEST TIPP: =A0Das passiert, wenn vor=FCbergehend
> wal_level=3Dminimal gesetzt wurde, ohne ein neues Base-Backup zu erzeugen.
> 2012-05-21 12:38:38 CEST LOG: =A0konsistenter Wiederherstellungszustand
> erreicht bei 0/15FBB78
> 2012-05-21 12:38:38 CEST LOG: =A0Datensatz mit L=E4nge null bei 0/15FBB78
> 2012-05-21 12:38:39 CEST FATAL: =A0das Datenbanksystem startet
> 2012-05-21 12:38:40 CEST FATAL: =A0das Datenbanksystem startet
> 2012-05-21 12:38:41 CEST FATAL: =A0das Datenbanksystem startet
> 2012-05-21 12:38:42 CEST FATAL: =A0das Datenbanksystem startet
> 2012-05-21 12:38:43 CEST FATAL: =A0das Datenbanksystem startet
> 2012-05-21 12:38:44 CEST FATAL: =A0das Datenbanksystem startet
>
> The base backup was created with following settings in postgresql.conf:
> wal_level =3D archive
> archive_mode =3D on
> archive_command =3D 'copy....

My German isn't very good, but it looks like you took this backup with
wal_level=3Dminimal, which is no good.

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