Simon Riggs wrote:
On Mon, 2008-02-11 at 09:29 +0100, Hans-Juergen Schoenig wrote:
Last week we have seen a problem with some horribly configured
machine.
The disk filled up (bad FSM ;) ) and once this happened the sysadmi
killed the system (-9).
After two days PostgreSQL has still not
On Feb 11, 2008, at 10:26 AM, Heikki Linnakangas wrote:
Hans-Juergen Schoenig wrote:
Last week we have seen a problem with some horribly configured
machine.
The disk filled up (bad FSM ;) ) and once this happened the
sysadmi killed the system (-9).
After two days PostgreSQL has still not
Heikki Linnakangas [EMAIL PROTECTED] writes:
Hans-Juergen Schoenig wrote:
that's where it finished, nothing else was logged between the redo
done and the last log messages
I bet you've bumped into a bug in gist redo code, the cleanup phase
shouldn't take long.
That's what it smells like
On Mon, 2008-02-11 at 10:44 +0100, Hans-Juergen Schoenig wrote:
On Feb 11, 2008, at 10:26 AM, Heikki Linnakangas wrote:
Wait, are you saying that the time was spent in the rm_cleanup
phase? That sounds unbelievable. Surely the time was spent in the
redo phase, no?
redo was done fast ...
Hans-Juergen Schoenig wrote:
this is he last info which was issued ...
nothing in between ...
during the rm_cleanup() nothing was logged into the logs. this is the
last log from today dawn:
[2008-02-11 03:45:16 CET ]LOG: lost parent for block 8558565
[2008-02-11 03:45:16 CET ]LOG: index
Last week we have seen a problem with some horribly configured machine.The disk filled up (bad FSM ;) ) and once this happened the sysadmi killed the system (-9).After two days PostgreSQL has still not started up and they tried to restart it again and again making sure that the consistency check
On Mon, 2008-02-11 at 11:50 +0100, Hans-Juergen Schoenig wrote:
I have that feeling too - it could very well be some Gist issue in
here but given what we have seen in the debugger this was not too
obvious.
At first glance it rather felt like a full check of the entire index.
Yeh, I'm happy
On Mon, 2008-02-11 at 09:29 +0100, Hans-Juergen Schoenig wrote:
Last week we have seen a problem with some horribly configured
machine.
The disk filled up (bad FSM ;) ) and once this happened the sysadmi
killed the system (-9).
After two days PostgreSQL has still not started up and they tried
Hans-Juergen Schoenig wrote:
Last week we have seen a problem with some horribly configured machine.
The disk filled up (bad FSM ;) ) and once this happened the sysadmi killed the
system (-9).
After two days PostgreSQL has still not started up and they tried to restart it
again and again
