Re: Killing a session on windows

From: Richard Huxton <dev(at)archonet(dot)com>
To: Howard Cole <howardnews(at)selestial(dot)com>
Cc: 'PgSql General' <pgsql-general(at)postgresql(dot)org>
Subject: Re: Killing a session on windows
Date: 2007-11-29 11:08:22
Message-ID: 474E9DA6.3000701@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Howard Cole wrote:
>
> I have a database I want to drop on a windows server. Unfortunately I
> cannot restart postgres because it is running several live database.
>
> To kill the offending session, I tried select * from pg_stat_activity to
> find the PID of the session, and then tried to kill it with command line:
>
> taskkill /f /pid 1234
>
> This appeared to kill the session, but postgres still thinks the session
> is live with the same process id.

Hmm - some signalling glitch presumably. Was it not possible to identify
the client and disconnect that?

> Using the SysInternals process explorer - there doesn't appear to be a
> process with the given ID.
>
> How can I get postgres to drop this session?

You could try pg_cancel_backend() - not sure what happens if it can't
find the process though.

http://www.postgresql.org/docs/8.2/static/functions-admin.html

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bill Bartlett 2007-11-29 11:22:02 Re: Killing a session on windows
Previous Message Richard Huxton 2007-11-29 11:04:58 Re: [Re] Re: [Re] Re: [Re] Re: [Re] Re: Unknown winsock error 10061while dumping a big database