Received: from MAIL01.stbernard.com (mail01.stbernard.com [64.154.93.162]) by postgresql.org (Postfix) with ESMTP id 0F77F474E42; Fri, 29 Mar 2002 17:04:25 -0500 (EST) Received: by MAIL01.stbernard.com with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Mar 2002 14:08:05 -0800 Message-ID: <7C760DAA511DC74B99E7D22189F786F1906DE2@MAIL01.stbernard.com> From: Jie Liang To: 'Bruce Momjian' , Tom Lane Cc: "'admin-sql@postgresql.org'" , pgsql-sql@postgresql.org Subject: dead session terminate Date: Fri, 29 Mar 2002 14:08:04 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200203/387 X-Sequence-Number: 7261 I don't how to put this question in a right way: I have a web application client to communicate with postgreSQL-7.1.3, in the case the application get crash, which sometime happens. The GUI of my application is disappear, I check my backend process, the connection which was done by my application is still there, is there a programatic way, I can cleanup those dead sessions, does postgreSQL have a way to terminate those dead sessions by timeout? My current solution is to use 'kill pid' under FreeBSD4.3, I don't think it's a good solution. The side effect of exiting those dead session is to keep my user waiting, I don't know why, but it does, I think it's wierd. Thanks. Jie Liang Software Engineer St. Bernard Software 16882 W. Bernardo Dr. San Diego, CA 92127 Tel: 858-524-2134 Fax:858-676-2228 jie@stbernard.com