On Sat, Jul 16, 2011 at 8:59 AM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Ken Caruso <k...@ipl31.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? > Sorry, the actual error reported by CLUSTER is: gpup=> cluster verbose tablename; INFO: clustering "dbname.tablename" WARNING: could not write block 12125253 of base/2651908/652397108 DETAIL: Multiple failures --- write error might be permanent. ERROR: could not open file "base/2651908/652397108.1" (target block 12125253): No such file or directory CONTEXT: writing block 12125253 of relation base/2651908/652397108 Thanks -Ken > > regards, tom lane >
