Skip site navigation (1) Skip section navigation (2)

hanging processes

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: hanging processes
Date: 2005-07-28 20:51:14
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3417DCF4D@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
I think this is windows specific but it might now be.  

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.

With any 'soft' method of killing the client up to and including killing
the client application process from the client task manager and
everything is normal in that the database logs a unexpected connection
closure and everything is cleaned up.

Is this normal?  

Merlin

Responses

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2005-07-29 04:20:06
Subject: Re: hanging processes
Previous:From: Audrey Bergeron-MorinDate: 2005-07-28 20:25:32
Subject: Re: Can't connect after restart

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group