| From: | Deven Phillips <deven(dot)phillips(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: DB Corruption after running out of disk space? |
| Date: | 2016-10-14 10:51:34 |
| Message-ID: | CAJw+4NA8U+0fDLMC7ztARFCUN4FRPh_1EkHs22YS78NasEDCeg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
NVM, I guess that I just didn't wait long enough for the re-index operation
to complete... We're good now...
On Fri, Oct 14, 2016 at 6:45 AM, Deven Phillips <deven(dot)phillips(at)gmail(dot)com>
wrote:
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | t.dalpozzo@gmail.com | 2016-10-14 12:34:29 | journaled FS and and WAL |
| Previous Message | Deven Phillips | 2016-10-14 10:45:53 | DB Corruption after running out of disk space? |