Received: from maia.hub.org (maia-4.hub.org [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 4870E633877
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri,  7 May 2010 05:04:13 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 30958-05 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri,  7 May 2010 08:04:05 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from elitecore.com (mailhost.elitecore.com [203.88.135.194])
	by mail.postgresql.org (Postfix) with ESMTP id E56CE632AA7
	for <pgsql-admin@postgresql.org>; Fri,  7 May 2010 05:04:04 -0300 (ADT)
Received: (qmail 2098 invoked from network); 7 May 2010 08:04:02 -0000
Received: from router.elitecore.com (HELO [192.168.1.136])
	(siddharth.shah@[203.88.135.193])
	(envelope-sender <siddharth.shah@elitecore.com>)
	by elitecore.com (qmail-ldap-1.03) with SMTP
	for <pgsql-admin@postgresql.org>; 7 May 2010 08:04:02 -0000
Message-ID: <4BE3C93C.70800@elitecore.com>
Date: Fri, 07 May 2010 13:33:08 +0530
From: Siddharth Shah <siddharth.shah@elitecore.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: pgsql-admin@postgresql.org,  pgsql-novice@postgresql.org
Subject: ERROR:  XX001 (Critical and Urgent)
Content-Type: multipart/alternative;
	boundary="------------080709060004000102080909"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.909 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201005/89
X-Sequence-Number: 34562

This is a multi-part message in MIME format.
--------------080709060004000102080909
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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

--------------080709060004000102080909
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello All,<br>
    <br>
    Getting <b>ERROR:  XX001: could not read block 17 of relation
base/16386/2619: read only 0 of 8192 bytes</b>, While vacuuming database<br>
    Manual vacuuming and Auto vacuuming process <b>constantly</b>
taking high CPU, not able to skip corrupted table for vacuuming and
dump this message at regular interval. <b> fsync is off</b> , From
strace, found that semop call was in infinite loop.<br>
      <br>
    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)<br>
    and not any error / warning from postgres daemon<br>
<br>
    Postgres Version : 8.4.3 (Migrated data from 8.4.1)<br>
<br>
What can be issue ? Is it issue coming after database  table
corruption, Can fsync on can prevent such (corruption) scenarios ?<br>
<br>
Thanks,<br>
Siddharth
</body>
</html>

--------------080709060004000102080909--