From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Steve Pribyl <Steve(dot)Pribyl(at)akunacapital(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: backup.old |
Date: | 2015-10-07 19:25:48 |
Message-ID: | CAKFQuwbuOHVYfBZqNjB5FtJKBCE3A3bcyAMXY34evK-W7CajVA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 7, 2015 at 3:16 PM, Steve Pribyl <Steve(dot)Pribyl(at)akunacapital(dot)com>
wrote:
> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Mamin | 2015-10-07 19:27:41 | Re: Best practices for aggregate table design |
Previous Message | Paul Ramsey | 2015-10-07 19:25:37 | PostGIS 2.2.0 Released |