From: | "Thomas H(dot)" <me(at)alternize(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Howard Cole <howardnews(at)selestial(dot)com>, 'PgSql General' <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Killing a session in windows |
Date: | 2007-12-12 13:33:40 |
Message-ID: | 475FE334.6090102@alternize.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Ashish Karalkar | 2007-12-12 13:35:08 | Re: very slow query |
Previous Message | Martin Gainty | 2007-12-12 13:32:05 | Re: Creating Aggregate functions in PLpgSQL |