Honestly I don't know. It was either pg_dump or a recovery script, that would have included a call to pg_start_backup. It does have the start_backup looking format. START WAL LOCATION: F3/1000028 (file 00000045000000F300000001) CHECKPOINT LOCATION: F3/1000060 BACKUP METHOD: pg_start_backup BACKUP FROM: master START TIME: 2015-05-30 01:39:24 CDT LABEL: base-backup Steve Pribyl Sr. Systems Engineer steve.pribyl@xxxxxxxxxxxxxxxx Desk: 312-994-4646 ________________________________________ From: pgsql-general-owner@xxxxxxxxxxxxxx <pgsql-general-owner@xxxxxxxxxxxxxx> on behalf of John R Pierce <pierce@xxxxxxxxxxxx> Sent: Tuesday, October 6, 2015 10:43 PM To: pgsql-general@xxxxxxxxxxxxxx Subject: Re: backup.old On 10/6/2015 8:28 PM, Steve Pribyl wrote: > What do I need to do to recover a database server that has a backup.old file in the data_directory. I have see references to a database being stopped during a backup and/or a second backup running and moving the old file aside, but it was not clear to me what needs to be done do recover. > > postgresql-9.3 9.3.0-2.pgdg12.4+1 what method or software were you using to perform this backup? -- john r pierce, recycling bits in santa cruz -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general ________________________________ [http://www.akunacapital.com/images/akuna.png] Steve Pribyl | Senior Systems Engineer Akuna Capital LLC 36 S Wabash, Suite 310 Chicago IL 60603 USA | www.akunacapital.com <http://www.akunacapital.com> p: +1 312 994 4646 | m: | f: +1 312 750 1667 | Steve.Pribyl@xxxxxxxxxxxxxxxx Please consider the environment, before printing this email. This electronic message contains information from Akuna Capital LLC that may be confidential, legally privileged or otherwise protected from disclosure. This information is intended for the use of the addressee only and is not offered as investment advice to be relied upon for personal or professional use. Additionally, all electronic messages are recorded and stored in compliance pursuant to applicable SEC rules. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, printing or any other use of, or any action in reliance on, the contents of this electronic message is strictly prohibited. If you have received this communication in error, please notify us by telephone at (312)994-4640 and destroy the original message. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general