Magnus Hagander wrote:
PostgreSQL will also not recover on its own (e.g; auto restart and
roll through the logs).
What do you mean by this? It doesn't start upon reboot?
What is needed
to make it start?
It means that postgresql doesn't recover on its own. On linux
if a backend crashes all of PostgreSQL will restart and come
back up if it can.
On Win32 it doesn't.
Ah, I thought you meant that the database recovery process (that runs
after a crash) failed and lost data. But it's not data-loss then, it
just took a reboot to fix it?
Right, but "just took a reboot to fix it" isn't very confidence inspiring ;)
I think we're somehow seeing a complete postmaster hang, where it's
either not able to kill off th ebackends as required, or just not
capable of accepting new connections after that. Which makes a
stacktrace from the postmaster the most interesting one to look at.
I have asked the customer to also look and see if there was one
particular process that was eating cpu via the task master and see if
that process can be killed. If that process can be killed and postgresql
comes back clean, then that is a step.
However, debugging this beast is a pain. I take it mingw doesn't have a
gdb we can use?
//Magnus
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
