Re: DB crash SOS - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: DB crash SOS
Date
Msg-id 6E9A4990-5913-42FA-BAA7-E72AFE2EA274@phlo.org
Whole thread Raw
In response to DB crash SOS  (Felde Norbert <fenor77@gmail.com>)
List pgsql-hackers
On Jun 17, 2010, at 10:39 , Felde Norbert wrote:
> I tried even with a bigger empty clog/0003 file but 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

Hm, you could try to make the clog/0003 file 256kB. Thats the maximum size of clog segments.

best regards,
Florian Pflug





pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: modular se-pgsql as proof-of-concept
Next
From: Robert Haas
Date:
Subject: Re: pg_dump does not honor namespaces when functions are used in index