Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id D0EC6633118 for ; Mon, 23 Aug 2010 21:17:11 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 16874-02 for ; Tue, 24 Aug 2010 00:17:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 918886330A0 for ; Mon, 23 Aug 2010 21:17:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o7O0H2Ku016190; Mon, 23 Aug 2010 20:17:02 -0400 (EDT) To: Kieren Scott cc: pgsql-admin@postgresql.org Subject: Re: WAL and archive disks full In-reply-to: References: Comments: In-reply-to Kieren Scott message dated "Mon, 23 Aug 2010 21:21:54 -0000" Date: Mon, 23 Aug 2010 20:17:02 -0400 Message-ID: <16189.1282609022@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201008/162 X-Sequence-Number: 35411 Kieren Scott 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