From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de>
To: pgsql-admin@postgresql.org
Subject: Re: SQLSTATE 53100 could not extend file / disk full
Date: Mon, 07 May 2012 12:09:49 -0500
Message-ID: <4FA7BB8D0200002500047925@gw.wicourts.gov> (raw)
In-Reply-To: <20120507120330.3010@gmx.net>
References: <20120507120330.3010@gmx.net>
"Jan-Peter Seifert" <Jan-Peter.Seifert@gmx.de> wrote:
> I wonder whether extra measures are necessary to recover from a
> disk full error besides freeing enough disk space?
> Is it no problem if the WAL is within the same disk space and
> can't be written as well?
> Should you free enough disk space, do a checkpoint, restart the
> server and check the server log?
At our shop, we have rarely run out of disk space on a production
machine, due to close monitoring; but in those few cases, and in the
somewhat more frequent case that it happened in a development
environment, we have simply freed space and continued. From what I
have seen, the PostgreSQL development community tries very hard to
ensure that you can do this safely. On the other hand, it would
obviously be very hard to thoroughly test every possible code path
under such conditions, so I always try to watch for possible
problems afterward.
-Kevin
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: Kevin.Grittner@wicourts.gov, Jan-Peter.Seifert@gmx.de
Subject: Re: SQLSTATE 53100 could not extend file / disk full
In-Reply-To: <4FA7BB8D0200002500047925@gw.wicourts.gov>
* 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