Обсуждение: pg_xlog/archive_status clean up
On Tue, Jan 9, 2018 at 4:58 PM, Ramiro Barreca <rbarreca@gmail.com> wrote:
At this moment I can see there are over 1.3 million "*.done" files at pg_xlog/archive_status folder.The first ones are there since 2013.As you may suppose this server has been rebooted several times since then. And daily backups are generated.Is it safe to remove the old ones manually without exposing data lost?What about to hold only last month ones?I think so but it would be better to have your approval.
It looks like there is an issue with your archive destination where these archives file accumlated under archive_status are not getting copied, hence they are not cleaned up automatically by PostgreSQL behavour & we dont' recommend to remove them manully as these get cleaned up when u resolve your archive destination.
Note: We highly recommend to review your environment from the PostgreSQL side
Ramiro Barreca
rbarreca@gmail.com
The WAL segments are copied by the archive_command to a remote mounted folder.
Do I have to create an "archive_status" folder within this remote folder so they can be copied automatically there?
I have created right now, but it is still empty.
Ramiro Barreca
rbarreca@gmail.com
rbarreca@gmail.com
2018-01-09 8:48 GMT-03:00 Shreeyansh Dba <shreeyansh2014@gmail.com>:
On Tue, Jan 9, 2018 at 4:58 PM, Ramiro Barreca <rbarreca@gmail.com> wrote:At this moment I can see there are over 1.3 million "*.done" files at pg_xlog/archive_status folder.The first ones are there since 2013.As you may suppose this server has been rebooted several times since then. And daily backups are generated.Is it safe to remove the old ones manually without exposing data lost?What about to hold only last month ones?I think so but it would be better to have your approval.It looks like there is an issue with your archive destination where these archives file accumlated under archive_status are not getting copied, hence they are not cleaned up automatically by PostgreSQL behavour & we dont' recommend to remove them manully as these get cleaned up when u resolve your archive destination.Note: We highly recommend to review your environment from the PostgreSQL side--