From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Win32 hard crash problem |
Date: | 2006-09-05 20:57:42 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA0FB8B@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> >> 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?
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.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2006-09-05 21:07:32 | Re: Win32 hard crash problem |
Previous Message | Joshua D. Drake | 2006-09-05 20:55:12 | Re: Win32 hard crash problem |