| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <pg(at)fastcrypt(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Win32 hard crash problem |
| Date: | 2006-09-07 03:01:23 |
| Message-ID: | 20060907030123.GB603@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> Gregory Stark wrote:
> >"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> >>The only known resolution is to reboot Windows. Using the service
> >>control panel to shutdown postgresql will fail once the message is
> >>received. It is unknown if using the task master to individually
> >>kill processes will work.
> >
> >This contradicts your previous email about restarting the postmaster
> >working.
>
> No, it doesn't. I never said restarting the postmaster would work. I
> said rebooting windows, allows postgresql to come back up. Those are
> entirely different things.
Yup. It was me who said that restarting the postmaster solved the
problem. That's what Dave Cramer told me. But maybe Dave was not
certain about that -- he did use the word "reboot" and I asked for
confirmation about whether this was an actual reboot of the machine
or just a postmaster "reboot", and he said it was the latter. But this
may have been a suposition.
Sorry for the confusion.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-07 04:02:00 | Re: ECPG/OpenBSD buildfarm failures, take I |
| Previous Message | Christopher Browne | 2006-09-07 02:12:15 | Re: New Linux Filesystem: NILFS |