random backend crashes - how to debug ( Is crash dump handler released ? ) - Mailing list pgsql-general

From BangarRaju Vadapalli
Subject random backend crashes - how to debug ( Is crash dump handler released ? )
Date
Msg-id 3DF304319BFE284182A530654E026383189081855D@INHYWEXMB2.infor.com
Whole thread Raw
Responses Re: random backend crashes - how to debug ( Is crash dump handler released ? )  (Merlin Moncure <mmoncure@gmail.com>)
Re: random backend crashes - how to debug ( Is crash dump handler released ? )  (Craig Ringer <craig@postnewspapers.com.au>)
Re: random backend crashes - how to debug ( Is crash dump handler released ? )  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general

Hi Everybody,

 

      We are using PostGRE 8.4 version and experiencing random backend crashes. We have enabled logging and are able to see some logging happening in pg_log directory but not of much use. Here are the logs.

 

   2011-06-14 18:06:04 IST WARNING:  terminating connection because of crash of another server process

2011-06-14 18:06:04 IST DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2011-06-14 18:06:04 IST HINT:  In a moment you should be able to reconnect to the database and repeat your command.

2011-06-14 18:06:04 IST WARNING:  terminating connection because of crash of another server process

2011-06-14 18:06:04 IST DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2011-06-14 18:06:04 IST HINT:  In a moment you should be able to reconnect to the database and repeat your command.

2011-06-14 18:06:04 IST WARNING:  terminating connection because of crash of another server process

2011-06-14 18:06:04 IST DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

2011-06-14 18:06:04 IST HINT:  In a moment you should be able to reconnect to the database and repeat your command.

2011-06-14 18:06:04 IST WARNING:  terminating connection because of crash of another server process

2011-06-14 18:06:04 IST DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

 

  I searched online and found crash dump handler idea has been proposed and patch for that has already been released if I am not wrong. Could anyone please detail the steps to install crash dump handler in windows? Also could you please help me with the ways to debug the crashes happening as shown above.

 

Thanks,

Bangar Raju

 

 

pgsql-general by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: system command in dblink?
Next
From: Merlin Moncure
Date:
Subject: Re: random backend crashes - how to debug ( Is crash dump handler released ? )