Re: Vacuumdb error - corruption

> -----Original Message-----
> From: Bhella Paramjeet-PFCW67 [mailto:PBhella@Motorola.com]
> Sent: Thursday, April 24, 2008 1:13 PM
> To: Tom Lane
> Cc: pgsql-admin@postgresql.org; Subbiah Stalin-XCGF84
> Subject: Re: Vacuumdb error - corruption
>
>
> According to our sysadmin there are no bad disks on the emc storage.
So

EMC Storage? Is the Database sitting on NFS storage?


> what do you suggest we should do to narrow out the problem. Any help
> will be highly appreciated. I have looked into the postgres archives
and
> people have reported this problem but there were no responses as to
how
> they resolved this issue. Do you still think it is due to block
> corruption on disk? Please advice.
>
> Thanks
> Paramjeet Kaur
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Thursday, April 17, 2008 5:18 PM
> To: Bhella Paramjeet-PFCW67
> Cc: pgsql-admin@postgresql.org; Subbiah Stalin-XCGF84
> Subject: Re: [ADMIN] Vacuumdb error
>
> "Bhella Paramjeet-PFCW67" <PBhella@Motorola.com> writes:
> > We have our production postgres 8.0.10 database running on linux
> > x86_64 machine. Recently we have started getting an error from one
of
> > our database while running vacuumdb. We are not getting this error
> > during backups just only during vacuuming of a database. Can anyone
> > please help us figure out why we are getting this error and how we
can
>
> > get rid of it. Any help will be appreciated.
>
> > Here is the error:
> > tst_021 ERROR:  invalid page header in block 8 of relation
> > "securityevent_pkey"
>
> Well, since it's just an index, you should be able to fix it by
> reindexing.  But I'd worry a bit about what caused the corruption.
> 8.0.10 is not exactly current --- you should update to 8.0.latest.
> And running some memory and disk diagnostics might not be wasted
effort.
>
>             regards, tom lane