| From: | Siddharth Shah <siddharth(dot)shah(at)elitecore(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org, pgsql-novice(at)postgresql(dot)org |
| Subject: | ERROR: XX001 (Critical and Urgent) |
| Date: | 2010-05-07 08:03:08 |
| Message-ID: | 4BE3C93C.70800@elitecore.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-novice |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-05-07 13:35:58 | Re: ERROR: XX001 (Critical and Urgent) |
| Previous Message | Bruce Momjian | 2010-05-06 22:33:41 | Re: Possible 9.0 beta issue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-05-07 13:35:58 | Re: ERROR: XX001 (Critical and Urgent) |
| Previous Message | Mladen Gogala | 2010-05-06 12:59:33 | Re: how to continue after error in batch mode with psql |