From: Siddharth Shah <siddharth.shah@elitecore.com>
To: pgsql-admin@postgresql.org
To: pgsql-novice@postgresql.org
Subject: ERROR: XX001 (Critical and Urgent)
Date: Fri, 07 May 2010 13:33:08 +0530
Message-ID: <4BE3C93C.70800@elitecore.com> (raw)
Hello All,
Getting *ERROR: XX001: could not read block 17 of relation
base/16386/2619: read only 0 of 8192 bytes*, While vacuuming database
Manual vacuuming and Auto vacuuming process *constantly* taking high
CPU, not able to skip corrupted table for vacuuming and dump this
message at regular interval. * fsync is off* , From strace, found that
semop call was in infinite loop.
I have tried with making fsync on, Now manual vacuum process is
taking high CPU, Strace unable to show any results (may be dead lock
situation)
and not any error / warning from postgres daemon
Postgres Version : 8.4.3 (Migrated data from 8.4.1)
What can be issue ? Is it issue coming after database table corruption,
Can fsync on can prevent such (corruption) scenarios ?
Thanks,
Siddharth
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: siddharth.shah@elitecore.com, pgsql-novice@postgresql.org
Subject: Re: ERROR: XX001 (Critical and Urgent)
In-Reply-To: <4BE3C93C.70800@elitecore.com>
* 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