>> 2009-11-02 10:13:35 FATAL: could not access status of transaction 139856778
2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085" at offset 98304: Permission denied.
I faced this error before a week only. Fortunately we have a valid backup and we restored the file (0085) in pg_clog directory. In our case it is the corruption issue. Kindly check with permission and also under the /usr/local/pgsql/data/pg_clog directory whether the file (0085) is there or not ? If it is not there than try to reload it from the backup. At last you can touch the file and restart the database. However, in this case you will be lose your data.
-- Thanks
Sam Jas
--- On Tue, 3/11/09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
From: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: [ADMIN] Please Help... Service fails to start
To: "Hengky Lie" <hengkyliwandouw@gmail.com>
Cc: pgsql-admin@postgresql.org
Date: Tuesday, 3 November, 2009, 3:37 AM
Hengky Lie <
hengkyliwandouw@gmail.com> writes:
> 2009-11-02 10:13:35 FATAL: could not access status of transaction
> 139856778
> 2009-11-02 10:13:35 DETAIL: Could not read from file "pg_clog/0085"
> at offset 98304: Permission denied.
You need to fix that "Permission denied" problem. Either the file
really is marked as not readable by the postgres user, or (probably
more likely on Windows) you have some malfunctioning "antivirus"
software installed.
regards, tom lane
--
Sent via pgsql-admin mailing list (
pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Yahoo! India has a new look.
Take a sneak peek.
