Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 6F99C6334BD
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 23 Aug 2010 18:22:03 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 54100-04 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 23 Aug 2010 21:21:55 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from bay0-omc1-s17.bay0.hotmail.com (bay0-omc1-s17.bay0.hotmail.com
	[65.54.190.28])
	by mail.postgresql.org (Postfix) with ESMTP id 24A86633471
	for <pgsql-admin@postgresql.org>; Mon, 23 Aug 2010 18:21:55 -0300 (ADT)
Received: from BAY149-W37 ([65.54.190.61]) by bay0-omc1-s17.bay0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.4675);
	Mon, 23 Aug 2010 14:21:54 -0700
Message-ID: <BAY149-w37FF7BF1B4AF50BC7289BCAE820@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_f0cafb56-cd55-440c-87ec-a70ec0539fff_"
X-Originating-IP: [94.8.170.116]
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
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 23 Aug 2010 21:21:54.0161 (UTC)
	FILETIME=[35811610:01CB4309]
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.01 tagged_above=-10 required=5
	tests=BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201008/154
X-Sequence-Number: 35403

--_f0cafb56-cd55-440c-87ec-a70ec0539fff_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi=2C

What would be the best course of action for resolving a situation whereby y=
our=20
postgres instance had crashed due to the wal disk and archive wal disk beco=
ming 100% full? Say
your backups have been failing and your 'monitoring' had not reported it co=
rrectly.

You can't start the instance because it needs to write to the WAL disk (whi=
ch is full)=2C but if you
manually move WAL files off the WAL disk=2C the archiver will fail because =
it can't find WAL files it
needs to archive. The instance may also still be in backup mode=2C because =
the backups had not=20
completed due to the disk full situation.

Being new to postgres=2C im trying to understand what actions need to be ta=
ken to get the instance=20
back up and running without compromising recoverability...?

Thanks in advance.
 		 	   		  =

--_f0cafb56-cd55-440c-87ec-a70ec0539fff_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'>
Hi=2C<br><br>What would be the best course of action for resolving a situat=
ion whereby your <br>postgres instance had crashed due to the wal disk and =
archive wal disk becoming 100% full? Say<br>your backups have been failing =
and your 'monitoring' had not reported it correctly.<br><br>You can't start=
 the instance because it needs to write to the WAL disk (which is full)=2C =
but if you<br>manually move WAL files off the WAL disk=2C the archiver will=
 fail because it can't find WAL files it<br>needs to archive. The instance =
may also still be in backup mode=2C because the backups had not <br>complet=
ed due to the disk full situation.<br><br>Being new to postgres=2C im tryin=
g to understand what actions need to be taken to get the instance <br>back =
up and running without compromising recoverability...?<br><br>Thanks in adv=
ance.<br> 		 	   		  </body>
</html>=

--_f0cafb56-cd55-440c-87ec-a70ec0539fff_--