From: | Howard Cole <howardnews(at)selestial(dot)com> |
---|---|
To: | 'PgSql General' <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Killing a session in windows |
Date: | 2007-12-13 22:53:19 |
Message-ID: | 4761B7DF.1080101@selestial.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thomas H. wrote:
>
>> On Tue, Dec 11, 2007 at 05:50:46PM -0500, Tom Lane wrote:
>>> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>>>> Howard Cole wrote:
>>>>> I take it from the lack of response that nobody knows how to kill
>>>>> a connection from the postgresql side on windows?
>>>> You can't, short of sending a signal to the process or restarting the
>>>> service.
>>> Which you can do, no? I thought pg_ctl's kill option was invented
>>> specifically to make this less painful on Windows.
>>
>> It does, and it shuold work. But it's just as dangerous as using kill
>> directly on the backends on Unix, of course.
>
> wasn't the OP asking for a way to kill active connections to a db?
> afaik pgAdmin3 does provide this functionality:
>
> pgadmin3 > tools > server status
>
> there you can easily terminate connections & transactions to a
> particular db. works pretty well in my test, i can kill active
> connections and drop the db afterwards.
>
> regards,
> thomas
The pgadmin terminate connections never did anything on any of my
windows servers. I always assumed it was something geared towards nix
servers that never quite worked on windows???
I shall look into the pg_ctl options to see if the kill option does what
taskill cannot (thanks for the heads up on that)
Thanks all.
From | Date | Subject | |
---|---|---|---|
Next Message | Howard Cole | 2007-12-13 23:20:59 | Re: Killing a session in windows |
Previous Message | Howard Cole | 2007-12-13 22:32:59 | Re: Killing a session in windows |