.
We use this backup method for 3 years and nothing happend. Ok, I know,
we was lucky or something else, but I think it is long time if it is
so wrong.
Thank you for your suggestions and advices, I will see what can I do.
fenor
2010/6/18 Merlin Moncure :
> On Fri, Jun 18, 2010 at 4:55 AM, Fe
with default settings.
The fsync settings are the default.
fenor
2010/6/17 Merlin Moncure :
> On Thu, Jun 17, 2010 at 4:51 PM, Felde Norbert wrote:
>> The first error message was what I got after postgres crashed and I
>> tried to make a dump, run vacuum or tried somthing else
memory.
2010/6/17 Tom Lane :
> Felde Norbert writes:
>> 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
>
6/17 Scott Marlowe :
> On Wed, Jun 16, 2010 at 5:55 PM, Felde Norbert 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:
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 fil
