From: | CS DBA <cs_dba(at)consistentstate(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | recovering from "too many failures" wal error |
Date: | 2014-11-29 21:37:56 |
Message-ID: | 547A3CB4.7020609@consistentstate.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
All;
We have a postgresql 9.2 cluster setup to do continuous wal archiving.
We were archiving to a mount point that went offline. As a result the db
could not archive the wal files, we ended up with many many errors in
the logs indicating the file could not be archived:
WARNING: transaction log file "0000000100000FB100000050" could not be
archived: too many failures
So we caught the issue before the file system filled up, fixed the mount
point and I see wal files being added to the target wal archive
directory. However the pg_xlog directory does not seem to be shrinking,
there are currently 27,546 files in the pg_xlog directory and that
number is not changed in some time (since we fixed the mount point.
I assume the db will at some point remove the backed up files in the
pg_xlog dir, is this true? or do I need to intervene?
Thanks in advance
From | Date | Subject | |
---|---|---|---|
Next Message | Damian Dimmich | 2014-11-30 11:17:01 | i386 postgres on i686 debian with multiarch |
Previous Message | Bill Moran | 2014-11-29 20:35:22 | Re: When was ANALYZE run in the past? |