From: Kieren Scott <kierenscott@hotmail.com>
To: pgsql-admin@postgresql.org
Subject: WAL and archive disks full
Date: Mon, 23 Aug 2010 21:21:54 +0000
Message-ID: <BAY149-w37FF7BF1B4AF50BC7289BCAE820@phx.gbl> (raw)
Hi,
What would be the best course of action for resolving a situation whereby your
postgres instance had crashed due to the wal disk and archive wal disk becoming 100% full? Say
your backups have been failing and your 'monitoring' had not reported it correctly.
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. The instance may also still be in backup mode, because the backups had not
completed due to the disk full situation.
Being new to postgres, im trying to understand what actions need to be taken to get the instance
back up and running without compromising recoverability...?
Thanks in advance.
=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: kierenscott@hotmail.com
Subject: Re: WAL and archive disks full
In-Reply-To: <BAY149-w37FF7BF1B4AF50BC7289BCAE820@phx.gbl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox