From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ken Caruso <ken@ipl31.net>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: 9.0.4 Data corruption issue
Date: Sat, 16 Jul 2011 11:59:52 -0400
Message-ID: <27386.1310831992@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMg8r_rzsTn+pR0+A0xCXS73o5QsTdgsisW9AHG6jEm87r1FCQ@mail.gmail.com>
References: <CAMg8r_rzsTn+pR0+A0xCXS73o5QsTdgsisW9AHG6jEm87r1FCQ@mail.gmail.com>
Ken Caruso <ken@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?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ken@ipl31.net
Subject: Re: 9.0.4 Data corruption issue
In-Reply-To: <27386.1310831992@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox