Thread: BUG #2657: 8.2beta1: Startup failures on Windows platform

BUG #2657: 8.2beta1: Startup failures on Windows platform

From
"Juergen Zimmermann"
Date:
The following bug has been logged online:

Bug reference:      2657
Logged by:          Juergen Zimmermann
Email address:      Juergen.Zimmermann@HS-Karlsruhe.de
PostgreSQL version: 8.2beta1
Operating system:   Windows XP Prof. SP2
Description:        8.2beta1: Startup failures on Windows platform
Details:

%PGDATA%\pg_log\postgresql-2006-09-27_145834.log shows these log entries:

LOG:  Windows fopen("recovery.conf","r") failed: code 2, errno 2
LOG:  Windows fopen("pg_xlog/00000001.history","r") failed: code 2, errno 2
LOG:  Windows fopen("backup_label","r") failed: code 2, errno 2

Re: BUG #2657: 8.2beta1: Startup failures on Windows platform

From
"Magnus Hagander"
Date:
> The following bug has been logged online:
>=20
> Bug reference:      2657
> Logged by:          Juergen Zimmermann
> Email address:      Juergen.Zimmermann@HS-Karlsruhe.de
> PostgreSQL version: 8.2beta1
> Operating system:   Windows XP Prof. SP2
> Description:        8.2beta1: Startup failures on Windows platform
> Details:
>=20
> %PGDATA%\pg_log\postgresql-2006-09-27_145834.log shows these log
> entries:
>=20
> LOG:  Windows fopen("recovery.conf","r") failed: code 2, errno 2
> LOG:  Windows fopen("pg_xlog/00000001.history","r") failed: code 2,
> errno 2
> LOG:  Windows fopen("backup_label","r") failed: code 2, errno 2

This is not a problem. It's just debugging code left-over from a
different issue. The messages will be removed before the release.

//Magnus

Re: BUG #2657: 8.2beta1: Startup failures on Windows platform

From
Tom Lane
Date:
"Juergen Zimmermann" <Juergen.Zimmermann@HS-Karlsruhe.de> writes:
> %PGDATA%\pg_log\postgresql-2006-09-27_145834.log shows these log entries:

> LOG:  Windows fopen("recovery.conf","r") failed: code 2, errno 2
> LOG:  Windows fopen("pg_xlog/00000001.history","r") failed: code 2, errno 2
> LOG:  Windows fopen("backup_label","r") failed: code 2, errno 2

This is not a bug ... those are just some debugging messages we've added
temporarily.

            regards, tom lane