From: | Meszaros Attila <tilla(at)draconis(dot)csoma(dot)elte(dot)hu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Recovery error |
Date: | 2001-07-31 14:27:55 |
Message-ID: | Pine.LNX.4.21.0107311607400.26730-100000@draconis.csoma.elte.hu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Accidentally I've ran out of disk space during intensive database write
operations. At the begining the backend went to recovery mode a few times,
and continued the work, but finally it has terribly died
( Segfault at backend/utils/mmgr/mcxt.c 222 )
After this event, the recovery has stoped this way:
[version: postgres 7.1 beta6
OK, I know this is very old... I do the upgrade soon, but I am
interested in what this error message means, could this happen with the
newser versions and so on.....]
pgdevel(at)road:/home/postgreSQL/postgres7.1$ postgres -O -P -Ddata performance
DEBUG: database system shutdown was interrupted at 2001-07-31 16:05:04 CEST
DEBUG: CheckPoint record at (1, 2941129720)
DEBUG: Redo record at (1, 2936012956); Undo record at (1, 2936012808); Shutdown FALSE
DEBUG: NextTransactionId: 5699520; NextOid: 17895453
DEBUG: database system was not properly shut down; automatic recovery in progress...
DEBUG: redo starts at (1, 2936012956)
DEBUG: open(logfile 1 seg 179) failed: No such file or directory
DEBUG: redo done at (1, 3003121540)
FATAL 2: XLogWrite: write request is past end of log
pgdevel(at)road:/home/postgreSQL/postgres7.1$
Attila
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-07-31 14:56:36 | Re: [Fwd: Majordomo Delivery Error] |
Previous Message | Timothy H. Keitt | 2001-07-31 13:48:52 | [Fwd: Majordomo Delivery Error] |