| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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-05 23:38:42 |
| Message-ID: | 44FE0A82.2080104@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> It sounds to me like we don't actually know that, because the client
> doesn't know how to restart the postmaster without rebooting the OS.
> (Josh says "pg_ctl stop" doesn't work in this state, which is a tad
> interesting in itself, because that doesn't go through a connection
> request.) It would be useful to try killing off the postgres processes
> via task manager and then see if a new postmaster can be started and if
> things then behave normally, or if a reboot is truly needed.
Right, and I have asked that the next time this happens that they try
and use the task manager to kill the process.
>
> The bottom line here is that all we have so far are client-side
> observations ("I get this message") and we have no clue what state
> the postmaster thinks it's in. We really need more information.
>
Yes, unfortunately there isn't much more to be had for another 2 weeks ;)
Sincerely,
Joshua D. Drake
> regards, tom lane
>
--
=== 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2006-09-06 00:29:09 | Re: Win32 hard crash problem |
| Previous Message | Tom Lane | 2006-09-05 23:36:04 | Re: Win32 hard crash problem |