X-Original-To: pgsql-bugs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 883E63A3CA5 for ; Fri, 5 Nov 2004 16:02:34 +0000 (GMT) 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 64701-03 for ; Fri, 5 Nov 2004 16:02:33 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id B9C433A3CE9 for ; Fri, 5 Nov 2004 16:02:32 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iA5G2Su5026615; Fri, 5 Nov 2004 11:02:28 -0500 (EST) To: =?iso-8859-2?B?U1rbQ1MgR+Fib3I=?= Cc: pgsql-bugs@postgresql.org Subject: Re: Killed backend won't rollback transaction? In-reply-to: <013b01c4c347$195212c0$0403a8c0@fejleszt4> References: <012601c4c292$6804b810$0403a8c0@fejleszt4> <26896.1099590388@sss.pgh.pa.us> <011201c4c33b$7bd722c0$0403a8c0@fejleszt4> <013b01c4c347$195212c0$0403a8c0@fejleszt4> Comments: In-reply-to =?iso-8859-2?B?U1rbQ1MgR+Fib3I=?= message dated "Fri, 05 Nov 2004 15:52:39 +0100" Date: Fri, 05 Nov 2004 11:02:28 -0500 Message-ID: <26614.1099670548@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/61 X-Sequence-Number: 9832 =?iso-8859-2?B?U1rbQ1MgR+Fib3I=?= writes: > BUT if I kill the first transaction (with standard (15 Terminate) signal), > the second one stucks in "waiting". SIGTERM on individual backends is not recommended or supported. FWIW, though, I could not duplicate this bug report. Are you sure you know what the second one was really waiting on? regards, tom lane