From: Guido Barosio <gbarosio@gmail.com>
To: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: Robert D Oden <roden@dbasetek.com>
Cc: PgSQL ADMIN <pgsql-admin@postgresql.org>
Subject: Re: Terminating a query that appears to be hung
Date: Mon, 29 Jan 2007 22:10:00 -0300
Message-ID: <f7f6b4c70701291710i7ff23781q49c324e11712aba8@mail.gmail.com> (raw)
In-Reply-To: <006601c743fe$31e824c0$79587cca@ITLaptop>
References: <45BE0CB1.5070308@dbasetek.com>
<006601c743fe$31e824c0$79587cca@ITLaptop>
Hmm, if you are a sysadmin you may want to get the process id for the
query, running something like:
Select procpid,current_query
from pg_stat_activity
where datname="dbname";
If you are running Linux, you'll get the procpid (pid) for the
offending query and by sending "kill -15 <pid>" you are
killing/terminating the query.
No idea on how to proceed if your platform is Windows.
Best wishes,
Guido Barosio
On 1/29/07, Phillip Smith <phillip.smith@weatherbeeta.com.au> wrote:
> Can youo be a bit more specific...? What client?
>
> Psql should terminate the connection when it exist. pgAdmin will close it
> when you exit the ap, or if you choose 'Disconnect' from the menu. In PHP
> you'll need to call pg_close function... Every 'client' will have a
> different method...
>
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Robert D Oden
> Sent: Tuesday, 30 January 2007 2:03 AM
> To: PgSQL ADMIN
> Subject: [ADMIN] Terminating a query that appears to be hung
>
> Is there a way to terminate a client session without having to restart
> Postgres.
>
> Thanks
>
> --
>
> Robert D Oden
> Database Marketing Technologies, Inc
> 951 Locust Hill Circle
> Belton MO 64012-1786
>
> Ph: 816-318-8840
> Fax: 816-318-8841
>
> roden@dbasetek.com
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>
>
> *******************Confidentiality and Privilege Notice*******************
>
> The material contained in this message is privileged and confidential to
> the addressee. If you are not the addressee indicated in this message or
> responsible for delivery of the message to such person, you may not copy
> or deliver this message to anyone, and you should destroy it and kindly
> notify the sender by reply email.
>
> Information in this message that does not relate to the official business
> of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
> Weatherbeeta, its employees, contractors or associates shall not be liable
> for direct, indirect or consequential loss arising from transmission of this
> message or any attachments
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
Guido Barosio
-----------------------
http://www.globant.com
guido.barosio@globant.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: gbarosio@gmail.com, phillip.smith@weatherbeeta.com.au, roden@dbasetek.com
Subject: Re: Terminating a query that appears to be hung
In-Reply-To: <f7f6b4c70701291710i7ff23781q49c324e11712aba8@mail.gmail.com>
References: <45BE0CB1.5070308@dbasetek.com> <006601c743fe$31e824c0$79587cca@ITLaptop> <f7f6b4c70701291710i7ff23781q49c324e11712aba8@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox