From: | Don Seiler <don(at)seiler(dot)us> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | OK to delete old .history files from archive? |
Date: | 2020-07-03 18:02:45 |
Message-ID: | CAHJZqBDLLeHk7=R9kdH0w+p16ujQ+EUf7TcX-2c82ks_n=9+YQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
TL;DR: Is it OK to delete .history files from WAL archive (wal-g/S3) that
are older than the oldest full backup?
Today we had restores fail complaining that they can't find timeline 21
when they should only be on timeline 1. The logs show them recovering 12+
.history files from the WAL archives. Looking at the archives, these
history files are all timestamped between last July and October. The
restore is from a full backup taken last night.
This happens to be the first restore after adding
"recovery_target_timeline='latest'" to our recovery.conf template. So I'm
guessing that PG just didn't bother with those old .history files before.
I believe these old .history files were just not properly cleaned up from
some exercises done last year on previous/other incarnations and are now
just polluting the WAL archive. I don't see why I would need .history files
that are nearly a year older than the backup I'm restoring from, but just
want to confirm it is safe to blow them all away.
Thanks,
Don.
--
Don Seiler
www.seiler.us
From | Date | Subject | |
---|---|---|---|
Next Message | Mahesh mana | 2020-07-04 05:03:04 | Work load manager... |
Previous Message | Peter Eisentraut | 2020-07-03 06:11:48 | Re: After renaming a database the subscription ( logical replication) stay sticky to the old database (master) |