[GENERAL] Tips for investigating DBMS failure

2000-10-16 Thread Karl DeBisschop
We had a production DBMS die in a failrly dramitica way this morning. I suspect the cause may have been interactions between lock and pg_dump, but I'm a long way off from being able to say that with any certainty at all. In the end, I moved the data directroy off to the side and restored all

Re: [GENERAL] Tips for investigating DBMS failure

2000-10-16 Thread Tom Lane
Karl DeBisschop <[EMAIL PROTECTED]> writes: > If it's of any use, I have attached the debug output - I don't see > where the problem is occurring, but I don't pretend to fully understand > the output, other than the exit is status 25. Signal 25?? What is that on your machine? (see /usr/includ

Re: [GENERAL] Tips for investigating DBMS failure

2000-10-16 Thread Vince Vielhaber
On Mon, 16 Oct 2000, Tom Lane wrote: > Karl DeBisschop <[EMAIL PROTECTED]> writes: > > If it's of any use, I have attached the debug output - I don't see > > where the problem is occurring, but I don't pretend to fully understand > > the output, other than the exit is status 25. > > Signal 25?