| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ken Caruso <ken(at)ipl31(dot)net> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: 9.0.4 Data corruption issue |
| Date: | 2011-07-16 15:59:52 |
| Message-ID: | 27386.1310831992@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ken Caruso <ken(at)ipl31(dot)net> writes:
> Had a DB that had bloated due to lots of updates and insuffcient auto vacuum
> settings. Attempted the following in the following order:
> VACUUM VERBOSE full tablename;
> CLUSTER tablename;
> Did the full first to ensure that the cluster had enough space to run.
> The db had already been previously clustered to an index. At some point
> during the VACUUM I started seeing the following errors in the logs:
> CONTEXT: writing block 12125253 of relation base/2651908/652397108
> WARNING: could not write block 12125253 of base/2651908/652397108
> DETAIL: Multiple failures --- write error might be permanent.
Ummm .... what's the actual ERROR?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken Caruso | 2011-07-16 19:42:47 | Re: 9.0.4 Data corruption issue |
| Previous Message | Ken Caruso | 2011-07-16 11:43:12 | Re: 9.0.4 Data corruption issue |