| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: hanging processes |
| Date: | 2005-07-29 12:19:52 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DCF51@Herge.rcsinc.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> > With a win32 server & XP clients, if the client is killed with a
hard
> > reset i.e. pull out power cord, the server does not recognize that
the
> > connection has been broken in pg_stat_activity and does not clean up
> > various things such as user_locks and presumably entries in
pg_listener.
> > A manual kill via pg_ctl is required from that point.
>
> Did you wait for the TCP KEEPALIVE timeout interval?
Apparently not. Timeout on windows is 2 hours which is pretty standard
I guess. I'm going to research into tweaking it down.
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-07-29 13:02:03 | Re: patch for win32 dynloader |
| Previous Message | Magnus Hagander | 2005-07-29 11:05:13 | Re: hanging processes |