Re: Possible database corruption - Mailing list pgsql-admin

From Craig Ringer
Subject Re: Possible database corruption
Date
Msg-id 50EB833C.4060206@2ndQuadrant.com
Whole thread Raw
In response to Possible database corruption - urgent  ("Benjamin Krajmalnik" <kraj@servoyant.com>)
Responses Re: Possible database corruption  ("Benjamin Krajmalnik" <kraj@servoyant.com>)
List pgsql-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

pgsql-admin by date:

Previous
From: "戴松晚"
Date:
Subject: How to implement the 'GRANT ALL ON DB1 TO 'USER'@'%' of MYSQL in PostgreSQL
Next
From: "Benjamin Krajmalnik"
Date:
Subject: Re: Possible database corruption