From: Kieren Scott <kierenscott@hotmail.com>
To: kevin.grittner@wicourts.gov
To: pgsql-admin@postgresql.org
Subject: Re: WAL and archive disks full
Date: Mon, 23 Aug 2010 23:04:49 +0000
Message-ID: <BAY149-w4522581F0D07AFE145D59AAE820@phx.gbl> (raw)
In-Reply-To: <4C72B2E70200002500034A85@gw.wicourts.gov>
References: <BAY149-w37FF7BF1B4AF50BC7289BCAE820@phx.gbl>
<4C72A63D0200002500034A80@gw.wicourts.gov>
<BAY149-w32A853DBBB87C2AD0C2DECAE820@phx.gbl>
<4C72B2E70200002500034A85@gw.wicourts.gov>
Thanks Kevin.
So if the wal filesystem is 100% full, can you actually startup postgres in archiving mode (so the archive process can resume copying)? Presumably postgres will try to write to the wal filesystem when you start it, and fail due to the filesystem full and then just shutdown/abort? 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.Grittner@wicourts.gov
> To: kierenscott@hotmail.com; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] WAL and archive disks full
>
> Kieren Scott <kierenscott@hotmail.com> 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. No need to apologize for contingency planning! :-)
>
> Hypothetically, in the situation where the stall originated with the
> application of files from the archive, fixing that end would and
> clearing files from the archive directory (or moving or deleting old
> ones if they were applying cleanly and just sitting there after
> application), would allow the archive process to resume copying and
> cleaning up files on the source database.
>
> If someone panicked and deleted files from the pg_xlog directory,
> well, the first thing is to try to make sure nobody does that. You
> might be able to turn off archiving and get the server to come up.
> If not, start by making a complete copy of your data directory and
> all of its subdirectories while PostgreSQL is stopped, because you
> may wander into trouble and want to try again. If you can't start
> with archiving turned off, you might want to look at this:
>
> http://www.postgresql.org/docs/current/interactive/app-pgresetxlog.html
>
> Of course, you want to monitor closely to ensure your backups are
> running correctly so you never need any of the above advice. ;-)
>
> -Kevin
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin =
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, kevin.grittner@wicourts.gov
Subject: Re: WAL and archive disks full
In-Reply-To: <BAY149-w4522581F0D07AFE145D59AAE820@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