Re: backup.old
Thank you very much. I read someplace if you run pg_start_backup twice the backup.old will be created, but there was not much beyond that and now I can't seem to find the reference.
From: David G. Johnston <david.g.johnston@gmail.com>
Sent: Wednesday, October 7, 2015 2:25 PM
To: Steve Pribyl
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] backup.old
Sent: Wednesday, October 7, 2015 2:25 PM
To: Steve Pribyl
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] backup.old
Great, dur(rtfm), so is it save to delete the backup.old, if the db is not in backup mode.
I don't see anything that would cause "backup.old" to be linked to an active backup if there was one in progress...and as far as I can tell a successfully completed backup doesn't leave around any such file either. So it should be safe to delete regardless of what pg_is_in_backup returns. If that returns true then I would be concerned that something (or someone) else is messing with the backup/data directory and that something likely also introduced backup.old
David J.
Steve Pribyl | Senior Systems Engineer
Akuna Capital LLC
36 S Wabash, Suite 310 Chicago IL 60603 USA | www.akunacapital.com
p: +1 312 994 4646 | m: | f: +1 312 750 1667 | Steve.Pribyl@akunacapital.com
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.
В списке pgsql-general по дате отправления: