Re: postgres crash SOS

Before I began I made a filesystem level backup after I stopped the
postgres service.
I have the original 0003 file, the size is 204800, The size of the
other files in this dir is 262144.

I corrected the permissions of the whole data dir, but the error
message is the same.
The exact messages:
The message is the same for the original pg_clog/0003, the 0003
containing binary 0 and after pg_resetxlog:
pg_dump: Error message from server: ERROR:  could not access status of
transaction 3974799
DETAIL:  Could not read from file "pg_clog/0003" at offset 204800: No error.
pg_dump: The command was: COPY public.active_sessions_split (ct_sid,
ct_name, ct_pos, ct_val, ct_changed) TO stdout;
pg_dump: *** aborted because of error


If create the bigger 0003 containing 0 than I get that:
pg_dump: Error message from server: ERROR:  xlog flush request
0/A19F5BF8 is not satisfied --- flushed only to 0/A02A1AC8
CONTEXT:  writing block 1149 of relation 1663/4192208/4192508
pg_dump: The command was: COPY public.history (historyid, adatkod,
elemid, userid, ido, actionid, targyid, szuloid, opvalue, longfield,
longtext) TO stdout;
pg_dump: *** aborted because of error

Thanks,
fenor

2010/6/17 Scott Marlowe <scott.marlowe@gmail.com>:
> On Wed, Jun 16, 2010 at 5:55 PM, Felde Norbert <fenor77@gmail.com> wrote:
>> Hi all,
>>
>> I use 8.2 on a windows server 2008.
>> Suddenly postgres crashed and I can not do anything. The message is
>> Could not access status of transaction 3982736.
>> DATAIL: Could not read from file "pg_clog/0003" at offset 204800: No error.
>>
>> The only one thing I found to correct this is to create a file filled
>> with binary 0 and replace clog/0003. Both files size are the same. I
>> tried that but I am still not able to run vacuum.
>
> Was the original 0003 file there, and if so what size was it?  Did you
> try to copy it out of the way first?  Did it belong to the pgsql user?
>  Did it have any attributes set that would make it impossible to read?
>  Are you running anti-virus on this machine? It's known to get in the
> way and cause these kinds of problems...
>
>  I tried even with a
>> bigger empty clog/0003 file, but nothing.
>> I tried to drop the last few transaction with pg_resetxlog and hoped I
>> can save some data, but the service wont start.
>> The last error message is:
>> ERROR: could not create relation 1663/0/1224: File exists. I looked
>> for base/1224/0/1663, base/1663/1224/0 and base/1663/0/1224 file but
>> there is no such file.
>>
>> Can anyone suggest something?
>> Many data would be lost if I can not repaire that so please!
>>
>> Thanks,
>> fenor
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>
>
>
> --
> When fascism comes to America, it will be intolerance sold as diversity.
>