From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kieren Scott <kierenscott(at)hotmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: WAL and archive disks full |
Date: | 2010-08-24 00:17:02 |
Message-ID: | 16189.1282609022@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Kieren Scott <kierenscott(at)hotmail(dot)com> writes:
> [ hypothetical scenario: ]
> You can't start the instance because it needs to write to the WAL disk
> (which is full), but if you manually move WAL files off the WAL disk,
> the archiver will fail because it can't find WAL files it needs to
> archive.
Uh, no, that shouldn't be a problem. You can manually move the same WAL
files that the archiver would move. Look into the
pg_xlog/archive_status subdirectory. Any WAL files that have a ".ready"
file in there can be moved to archive, and then you delete the .ready
file, and you're good to go.
Of course, if you don't have any .ready files, you're going to need to
look elsewhere for some disk space to reclaim :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Krajmalnik | 2010-08-24 04:15:34 | Re: pgBouncer for connection pooling |
Previous Message | Tom Lane | 2010-08-24 00:11:15 | Re: Unable to drop role |