| From: | Doug McNaught <doug(at)wireboard(dot)com> |
|---|---|
| To: | "Andrew Bartley" <abartley(at)evolvosystems(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: cannot read block 39 of pg_attribute_relid_attnam_index: Input/output error |
| Date: | 2002-03-17 23:56:06 |
| Message-ID: | m3adt6wxyh.fsf@varsoon.denali.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Andrew Bartley" <abartley(at)evolvosystems(dot)com> writes:
> I run a nightly cron that drops all of the application table indexes
> then unload and reload the most heavily used tables to ensure they
> are in key sequence, then vacuum analyse the whole DB, recreate the
> indexes and triggers.
>
> Over the weekend, this error appeared.
>
> ERROR: cannot read block 39 of pg_attribute_relid_attnam_index:
> Input/output error vacuumdb: vacuum evolvo failed
>
> Could this be a physical I/O error?
Most likely yes. Check your syslogs for kernel i/o error messages.
-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/
Custom software development, systems and network consulting.
Java PostgreSQL Enhydra Python Zope Perl Apache Linux BSD...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2002-03-18 00:08:13 | Re: limit /offset |
| Previous Message | Martijn van Oosterhout | 2002-03-17 23:55:45 | Re: Why is it not using an index? |