On 11/29/2014 3:37 PM, CS DBA wrote:
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 what I recall from this list, you should never play in pg_xlog. You'll probably do more damage than good. PG should take care of itself.
Are you still getting error messages? Looks like its been a few days, has it shrunk yet?
-Andy -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
