| From: | Craig Ringer <craig(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Benjamin Krajmalnik <kraj(at)servoyant(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Possible database corruption |
| Date: | 2013-01-08 02:23:56 |
| Message-ID: | 50EB833C.4060206@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Krajmalnik | 2013-01-08 02:30:57 | Re: Possible database corruption |
| Previous Message | 戴松晚 | 2013-01-08 02:15:30 | How to implement the 'GRANT ALL ON DB1 TO 'USER'@'%' of MYSQL in PostgreSQL |