BUG #13642: no backup_label file in PG_DATA after pg_stop_backup(); - Mailing list pgsql-bugs

From amir.rohan@mail.com
Subject BUG #13642: no backup_label file in PG_DATA after pg_stop_backup();
Date
Msg-id 20150926031617.3022.6412@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #13642: no backup_label file in PG_DATA after pg_stop_backup();  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      13642
Logged by:          Amir Rohan
Email address:      amir.rohan@mail.com
PostgreSQL version: 9.4.4
Operating system:   Linux
Description:

SELECT pg_start_backup('backup1');
SELECT pg_stop('backup1');

Doesn't create the `backup_label`  described in the docs (I'm assuming
"cluster directory" means data directory, e.g. $PGDATA):
http://www.postgresql.org/docs/current/static/continuous-archiving.html

They further state:
"The file is critical to the integrity of the backup, should you need to
restore from it."

Are my backups safe or not?

pgsql-bugs by date:

Previous
From: it@ramsoft.com
Date:
Subject: BUG #13641: PostgreSQL (pg_ctl.exe) conflicts with GPClient.exe
Next
From: amir.rohan@mail.com
Date:
Subject: BUG #13643: Should a process dying bring postgresql down, or not?