On Thu, Feb 14, 2013 at 3:01 AM, Ian Lawrence Barwick
<barwick@gmail.com> wrote:
Thanks Ian
I figured it out and figured out a way around it for now.
My archive destination had it's ownership changed and thus the archive command could not write to the directory. I didn't catch this until well it was too late. So 225GB, 27000 files later.
I found a few writeups on how to clear this up and use the command true in the archive command to quickly and easily delete a bunch of wal files from the pg_xlog directory in short order. So that worked and now since I know what the cause was, I should be able to restore my pg_archive PITR configs and be good to go.
This is definitely one of those bullets I would rather not of taken, but the damage appears to be minimal (thank you postgres)
Thanks again
Tory