Vadim Mikheev wrote:
There's a report of startup recovery failure in Japan.
Redo done but ...
Unfortunately I have no time today.
Please ask to start up with wal_debug = 1...
Isn't it very difficult for dbas to leave the
corrupted database as it is ?
ISTM we could hardly expect to
.
- Original Message -
From: "Hiroshi Inoue" [EMAIL PROTECTED]
To: "Vadim Mikheev" [EMAIL PROTECTED]
Cc: "pgsql-hackers" [EMAIL PROTECTED]
Sent: Monday, April 30, 2001 11:02 PM
Subject: Re: [HACKERS] 7.1 startup recovery failure
Vadim Mikheev wrote:
There'
"Mikheev, Vadim" wrote:
There's a report of startup recovery failure in Japan.
DEBUG: redo done at (1, 3923880100)
FATAL 2: XLogFlush: request is not satisfied
postmaster: Startup proc 4228 exited with status 512 - abort
Is this person using 7.1 release, or a beta/RC
Hiroshi Inoue [EMAIL PROTECTED] writes:
There's a report of startup recovery failure in Japan.
DEBUG: redo done at (1, 3923880100)
FATAL 2: XLogFlush: request is not satisfied
postmaster: Startup proc 4228 exited with status 512 - abort
Is this person using 7.1 release, or a beta/RC
There's a report of startup recovery failure in Japan.
DEBUG: redo done at (1, 3923880100)
FATAL 2: XLogFlush: request is not satisfied
postmaster: Startup proc 4228 exited with status 512 - abort
Is this person using 7.1 release, or a beta/RC version? That looks
just like the
Hi,
There's a report of startup recovery failure in Japan.
Redo done but ...
Unfortunately I have no time today.
regards,
Hiroshi Inoue
KAMI wrote:
DEBUG: database system shutdown was interrupted at 2001-04-26 22:15:00 JST
DEBUG: CheckPoint record at (1, 3923829232)
DEBUG: Redo record
There's a report of startup recovery failure in Japan.
Redo done but ...
Unfortunately I have no time today.
Please ask to start up with wal_debug = 1...
Vadim
---(end of broadcast)---
TIP 2: you can get off all lists at once with the
