X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 310C99F9FE3 for ; Mon, 26 Jun 2006 12:26:10 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 89366-09 for ; Mon, 26 Jun 2006 12:26:02 -0300 (ADT) X-Greylist: delayed 00:16:44.543762 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id D2A2B9F9AD3 for ; Mon, 26 Jun 2006 12:26:01 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from infbssys.ips.cs.tu-bs.de (infbssys.ips.cs.tu-bs.de [134.169.32.1]) by svr4.postgresql.org (Postfix) with ESMTP id 312D15AF039 for ; Mon, 26 Jun 2006 15:09:15 +0000 (GMT) Received: from is38 (is38 [134.169.32.148]) by infbssys.ips.cs.tu-bs.de (8.13.6+Sun/8.13.6) with ESMTP id k5QF9Can020389 for ; Mon, 26 Jun 2006 17:09:12 +0200 (CEST) From: Thomas Mack To: pgsql-admin@postgresql.org Subject: Aborting transactions Date: Mon, 26 Jun 2006 17:09:11 +0200 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200606261709.11750.mack@ifis.cs.tu-bs.de> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/230 X-Sequence-Number: 22192 Hi, we use postgres for student's education and others. Now we had an issue with some SQL statement in connection with some triggers, that probably caused an infinite loop in processing for at least 10 hours or so on some two to ten line tables. Unfortunately, the students used the phpPgAdmin web interface, so they could not abort the running SQL statement. They could not even continue to work with the database from phpPgAdmin. So the question arose, how to abort running statements at least via the postgres account. I remember some methods from Ingres "some" years ago, but I did not find anything similar in postgresql. Is there any chance to monitor the current transactions and abort them, in case of need? Thanks, Thomas Mack TU Braunschweig, Institut f=FCr Informationssysteme