Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id E65CD9FB270 for ; Sat, 3 Feb 2007 04:24:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 59707-09 for ; Sat, 3 Feb 2007 04:24:29 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.228]) by postgresql.org (Postfix) with ESMTP id E38489FB1C4 for ; Sat, 3 Feb 2007 04:24:30 -0400 (AST) Received: by nz-out-0506.google.com with SMTP id i11so1071028nzh for ; Sat, 03 Feb 2007 00:24:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=YdgqOipEGqKKD3Kt9GvVdiH0pjJBzHSBOh5miOdoceLvKoAoUXj+OhkqpRNvn1+TBmHChA96QOXc1MgeTx1QRheFnXTtidSsE40MGFZWyGxFMx7VhjYKU3o6neu6ibSs7A3vQh1fMx2JsSM5PU3Csvt+Lvf63wleMGcDQ0706N4= Received: by 10.65.216.19 with SMTP id t19mr7463124qbq.1170491069208; Sat, 03 Feb 2007 00:24:29 -0800 (PST) Received: by 10.65.206.17 with HTTP; Sat, 3 Feb 2007 00:24:29 -0800 (PST) Message-ID: Date: Sat, 3 Feb 2007 13:24:29 +0500 From: "Shoaib Mir" To: "Robert D Oden" Subject: Re: Terminating a query that appears to be hung Cc: "Guido Barosio" , "Phillip Smith" , "PgSQL ADMIN" In-Reply-To: <45C3B431.4010003@dbasetek.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_22141_21370241.1170491069023" References: <45BE0CB1.5070308@dbasetek.com> <006601c743fe$31e824c0$79587cca@ITLaptop> <45C3B431.4010003@dbasetek.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/43 X-Sequence-Number: 24508 ------=_Part_22141_21370241.1170491069023 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Use SIGTERM for killing only one process. You can also use kill -INT. It sends a query cancel to the backend and will not disturb other processes and the database server. -- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 2/3/07, Robert D Oden wrote: > > Thank you for the response. We are using Linux and I am able to identify > the offending . I was not sure if killing the process was an > acceptable and safe practice. > > Thanks again! > Robert > > Guido Barosio wrote: > > 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 " 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 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 > >> > > > > > > -- > > 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 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > ------=_Part_22141_21370241.1170491069023 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Use SIGTERM for killing only one process. You can also use kill -INT. It sends a query cancel to the backend and will not disturb other processes and the database server.

--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 2/3/07, Robert D Oden < roden@dbasetek.com> wrote:
Thank you for the response. We are using Linux and I am able to identify
the offending <pid>. I was not sure if killing the process was an
acceptable and safe practice.

Thanks again!
Robert

Guido Barosio wrote:
> 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
>>
>
>

--

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 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

------=_Part_22141_21370241.1170491069023--