pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: mack@ifis.cs.tu-bs.de
To: tgl@sss.pgh.pa.us
Cc: pgsql-admin@postgresql.org
Subject: Re: Aborting transactions
Date: Mon, 26 Jun 2006 22:10:07 +0200
Message-ID: <44A03F1F.mailJHY11PP6J@ifis.cs.tu-bs.de> (raw)
In-Reply-To: <29951.1151338243@sss.pgh.pa.us>
References: <200606261709.11750.mack@ifis.cs.tu-bs.de>
	<29951.1151338243@sss.pgh.pa.us>

>Thomas Mack <mack@ifis.cs.tu-bs.de> writes:
>> Is there any chance to monitor the current transactions and abort them,
>> in case of need?
>
>Sure, just SIGINT whichever backend you want to cancel its query.
>Use "ps" or pg_stat_activity to figure out the right PID to kill.
>
I don't have a pg_stat_activity on this 7.4.6, so using ps gives me:

postgres@is20 ~ 4 > ps -ef | grep postmaster
postgres  4499  4498   0 08:59:18 ?           0:04 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 23268  4498   0 12:50:39 ?           0:03 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres  4713  4498   0 09:25:05 ?           0:05 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 20836  4498   0 15:22:51 ?           0:02 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 20859  4498   0 18:51:48 ?           0:01 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 25116  4498   0 13:40:26 ?           0:04 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 12050  4498   0 21:57:30 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres  4498  4489   0 08:59:18 ?           0:47 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 18589  4498   0 21:09:09 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 11104  4498   0 21:34:24 ?           0:03 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres  4500  4499   0 08:59:18 ?           0:48 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 14684  4498   0 19:46:16 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 25527  4498   0 13:47:25 ?           0:03 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 13863  4498   0 19:20:56 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 11910  4498   0 21:54:18 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 23450  4498   0 12:53:48 ?           0:05 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 24216  4498   0 13:16:27 ?           0:04 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 21584  4498   0 19:08:55 ?           0:01 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 25904  4498   0 13:54:19 ?           0:04 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 17848  4498   0 17:35:52 ?           0:01 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 10893  4498   0 21:28:04 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 12210 12147   0 22:02:27 pts/22      0:00 grep postmaster
postgres 18650  4498   0 21:10:34 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres  1563  4498   0 19:15:38 ?           0:01 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 16993  4498   0 20:26:05 ?           0:08 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 14210  4498   0 19:30:01 ?           0:10 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 14457  4498   0 19:38:37 ?           0:01 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 14030  4498   0 19:23:51 ?           0:01 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 16675  4498   0 20:18:21 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 14914  4498   0 19:49:00 ?           0:01 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres 17576  4498   0 20:41:26 ?           0:00 /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
postgres@is20 ~ 5 > 

So, what is what? I will switch to 8.1 later this year, is it better
with that version?

Best regards,
Thomas Mack
TU Braunschweig, Institut für Informationssysteme



view thread (7+ messages)  latest in thread

Message-ID: <44A03F1F.mailJHY11PP6J@ifis.cs.tu-bs.de>
Permalink:  ../44A03F1F.mailJHY11PP6J@ifis.cs.tu-bs.de/
Also on:    postgresql.org/message-id/44A03F1F.mailJHY11PP6J@ifis.cs.tu-bs.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mack@ifis.cs.tu-bs.de, tgl@sss.pgh.pa.us
  Subject: Re: Aborting transactions
  In-Reply-To: <44A03F1F.mailJHY11PP6J@ifis.cs.tu-bs.de>
  References: <200606261709.11750.mack@ifis.cs.tu-bs.de> <29951.1151338243@sss.pgh.pa.us> <44A03F1F.mailJHY11PP6J@ifis.cs.tu-bs.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox