Re: Killing a data modifying transaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: William Temperley <willtemperley(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Killing a data modifying transaction
Date: 2009-06-22 13:48:03
Message-ID: 15396.1245678483@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

William Temperley <willtemperley(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joel Nothman 2009-06-22 14:34:49 Re: Select ranges based on sequential breaks
Previous Message Abraham, Danny 2009-06-22 13:17:13 8.2 instance that won't come up after shutdown