From: Craig Ringer <craig@2ndQuadrant.com>
To: Benjamin Krajmalnik <kraj@servoyant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Possible database corruption
Date: Tue, 08 Jan 2013 10:23:56 +0800
Message-ID: <50EB833C.4060206@2ndQuadrant.com> (raw)
In-Reply-To: <F4E6A2751A2823418A21D4A160B6898892B7BB@fletch.stackdump.local>
References: <F4E6A2751A2823418A21D4A160B6898892B7BB@fletch.stackdump.local>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On 01/08/2013 05:22 AM, Benjamin Krajmalnik wrote:
>
> I have a situation where pg_xlog started growing until it filled up
> the disk drive.
>
This should not ever cause corruption. If it has, there's a bug at work.
A crash is reasonable (albeit undesirable; it'd be better to just report
errors on connections) - but database corruption is not.
Before doing ANYTHING else, read
http://wiki.postgresql.org/wiki/Corruption and act on it.
How big is the DB?
What file system is it on?
PostgreSQL 9.0.[what?] ?
Host OS?
Disk subsystem?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
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: craig@2ndQuadrant.com, kraj@servoyant.com
Subject: Re: Possible database corruption
In-Reply-To: <50EB833C.4060206@2ndQuadrant.com>
* 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