X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 09950D82C0 for ; Fri, 18 Nov 2005 07:34:32 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 00205-09 for ; Fri, 18 Nov 2005 11:34:34 +0000 (GMT) X-Greylist: delayed 00:20:49.813404 by SQLgrey- Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by svr1.postgresql.org (Postfix) with ESMTP id 5B33DDB96A for ; Fri, 18 Nov 2005 07:34:28 -0400 (AST) Received: from [192.168.2.101] (82.240.84.48) by mx.laposte.net (7.2.060.1) (authenticated as ah.pgsql) id 42F8D2C203E65B35 for pgsql-admin@postgresql.org; Fri, 18 Nov 2005 12:13:40 +0100 Message-ID: <437DB74C.2000400@laposte.net> Date: Fri, 18 Nov 2005 12:13:16 +0100 From: Armel HERVE User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Select waiting Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=2.151 required=5 tests=[RCVD_IN_WHOIS_INVALID=2.151] X-Spam-Score: 2.151 X-Spam-Level: ** X-Archive-Number: 200511/236 X-Sequence-Number: 19609 Hello there, when I have connections waiting, can I kill the root connection which is the origin of the lock, without restarting the postgres server ? I know it's not a good practice, but we are in a development step... Thanks for your answers (and sorry for my poor English :-) ) Armel