Thank you.
Kieren
> To: kierensc...@hotmail.com
> CC: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] WAL and archive disks full
> Date: Mon, 23 Aug 2010 20:17:02 -0400
> From: t...@sss.pgh.pa.us
>
> Kieren Scott writes:
> > [ hypothetical scenario: ]
>
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
? Wouldnt you have to free some
space in the wal filesystem in order to get postgres up and running?
Thanks for you help.
> Date: Mon, 23 Aug 2010 17:41:59 -0500
> From: kevin.gritt...@wicourts.gov
> To: kierensc...@hotmail.com; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] WAL
Kieren Scott wrote:
> Sorry it's a bit of a what-if scenario. I can envisage
> encountering a situation in the future whereby we hit this
> problem, and I was trying to put a plan in place for how to deal
> with it.
Oh, OK. I was afraid you had actually *hit* this situation and were
being coy
ing a situation
in the future
whereby we hit this problem, and I was trying to put a plan in place for how to
deal with it.
Thanks in advance.
> Date: Mon, 23 Aug 2010 16:47:57 -0500
> From: kevin.gritt...@wicourts.gov
> To: kierensc...@hotmail.com; pgsql-admin@postgresql.org
> S
Kieren Scott wrote:
> 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 c
