Thread: Problem with pg_log file corrupted

Hi,
I think the pg_log file of my postgreSQL is corrupted after a power
failure.
I can;t access to tables in my database now.
The error message appear when I tried to list all tables is as below :
" cannot flush block 8 of pg_log to stable store "
Anybody know how can I restore back the pg_log file.
Thanks.

Emmanuel Wong

YekFu.Wong@seagate.com writes:
> The error message appear when I tried to list all tables is as below :
> " cannot flush block 8 of pg_log to stable store "

I can't see any good reason why you'd get a failure there ... unless
maybe you are out of disk space?

Assuming you are running a 7.0.* release, I'd suggest updating to 7.0.3,
which will at least give a more detailed error message.

            regards, tom lane

---------------------- Forwarded by YekFu Wong on 04/26/2001 02:27 PM
---------------------------


YekFu Wong
04/26/2001 07:26 AM

To:   "Tom Lane" <tgl@sss.pgh.pa.us> @ INTERNET
cc:
Subject:  Re: [GENERAL] Problem with pg_log file corrupted  (Document link:
      YekFu Wong)


I am using postgreSQL version 6.5.3
I think probably the transaction was inconsistent when there is a power
failure
when user try to update data to tables through webpage.
Now, I can't do #pgaccess [database name] ....
It will prompt me the same error saying cannot flush block 8 of pg_log
file.....
Since pg_log file is a binary file, I don;t know how to restore it...
I tried to delete the file but then, I can;t open any database without the
file.
I am trying to upgrade the postgreSQL version now...see whether it helps.
Thanks.




"Tom Lane" <tgl@sss.pgh.pa.us>@postgresql.org on 04/26/2001 06:27:14 AM

Sent by:  pgsql-general-owner@postgresql.org


To:   YekFu.Wong@seagate.com
cc:   pgsql-general@postgresql.org
Subject:  Re: [GENERAL] Problem with pg_log file corrupted


YekFu.Wong@seagate.com writes:
> The error message appear when I tried to list all tables is as below :
> " cannot flush block 8 of pg_log to stable store "

I can't see any good reason why you'd get a failure there ... unless
maybe you are out of disk space?

Assuming you are running a 7.0.* release, I'd suggest updating to 7.0.3,
which will at least give a more detailed error message.

               regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly