Re: ERROR: could not access status of transaction 575
by bhurt@[EMAIL PROTECTED]
(Brian Hurt)
Jun 17, 2008 at 12:46 PM
This is a multi-part message in MIME format.
--------------020301020209000302070200
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Brian Hurt wrote:
>
> Hello all-
>
> I'm getting an error on a Postgres database when I access a table:
>
>> template0=# select * from pg_language;
>> ERROR: could not access status of transaction 575
>> DETAIL: could not open file "pg_clog/0000": No such file or directory
>> template0=#
>
More information: I did (as postgres):
dd bs=49152 count=1 if=/dev/zero of=/database/postgres/pg_clog/0000
to create the clog file (49152 is the size of
/database/postgres/pg_clog/0001), then fixed the permissions (chmod 0600
/database/postgres/pg_clog/0000). This seems to have fixed the problem.
The partition is on a Areca raid control, and some playing with the
areca cli didn't turn up any HD errors. We're running bonnie++ on the
partition to see if it detects any errors.
Brian
--------------020301020209000302070200
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Brian Hurt wrote:<br>
<blockquote cite="mid4857E233.7010509@[EMAIL PROTECTED]
" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<br>
Hello all-<br>
<br>
I'm getting an error on a Postgres database when I access a table:<br>
<br>
<tt>
<blockquote type="cite">template0=# select * from pg_language;<br>
ERROR: could not access status of transaction 575<br>
DETAIL: could not open file "pg_clog/0000": No such file or
directory<br>
template0=#</blockquote>
</tt></blockquote>
<tt><br>
</tt>More information: I did (as postgres):<br>
<br>
dd bs=49152 count=1 if=/dev/zero of=/database/postgres/pg_clog/0000<br>
<br>
to create the clog file (49152 is the size of
/database/postgres/pg_clog/0001), then fixed the permissions (chmod
0600 /database/postgres/pg_clog/0000). This seems to have fixed the
problem.<br>
<br>
The partition is on a Areca raid control, and some playing with the
areca cli didn't turn up any HD errors. We're running bonnie++ on
the
partition to see if it detects any errors.<br>
<br>
Brian<br>
<br>
</body>
</html>
--------------020301020209000302070200--
