DB Corruption after running out of disk space?

From: Deven Phillips <deven(dot)phillips(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: DB Corruption after running out of disk space?
Date: 2016-10-14 10:45:53
Message-ID: CAJw+4NDoKwXwjjdgT0_D+99LHiiKn6y5MaG6hMwfY84AbLZdFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Here's hoping someone can help me... Overnight, our primary database server
(part of a master/slave replication pair) ran out of disk space. I have
cleaned up space now, but while performing some VACUUM ANALYZE commands I
find that there is some corruption.

I'm getting messages like: ERROR: missing chunk number 0 for toast value
304627805 in pg_toast_16421

I searched around and previous posts to the mailing list suggested a
re-index of the pg_toast.pg_toast_16421 table, which I did to no effect.
Still getting the error.

Any suggestions or ideas would be appreciated.

Thanks in advance!

Deven Phillips

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Deven Phillips 2016-10-14 10:51:34 Re: DB Corruption after running out of disk space?
Previous Message Jaisingkar, Piyush 2016-10-14 06:52:30 Re: Passing of where clause to remote table in FDW