Re: Killing a data modifying transaction - Mailing list pgsql-general

From Tom Lane
Subject Re: Killing a data modifying transaction
Date
Msg-id 15396.1245678483@sss.pgh.pa.us
Whole thread Raw
In response to Killing a data modifying transaction  (William Temperley <willtemperley@gmail.com>)
Responses Re: Killing a data modifying transaction
List pgsql-general
William Temperley <willtemperley@gmail.com> writes:
> I've got two transactions I tried to kill 3 days ago using "select
> pg_cancel_backend(<pid>)", then SIGTERM, and have since then been
> using 100% of a cpu core each. They were supposed to insert the
> results of large unions with PostGIS and appear to have failed.
> Could someone tell me what's the least worst option here please? If I
> kill -9 will I corrupt my data directory?

No, you'll just lose all your open sessions.

It might be worth trying to identify where they're looping before
you zap them, though.  A stack trace from gdb would help.

            regards, tom lane

pgsql-general by date:

Previous
From: William Temperley
Date:
Subject: Killing a data modifying transaction
Next
From: "Abraham, Danny"
Date:
Subject: 8.2 instance that won't come up after shutdown