Killing a data modifying transaction

Поиск
Список
Период
Сортировка
От William Temperley
Тема Killing a data modifying transaction
Дата
Msg-id 439dc11e0906220554p721f9167m6db1028939557c42@mail.gmail.com
обсуждение исходный текст
Ответы Re: Killing a data modifying transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
Hi All,

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?  (I've searched for an
answer in the FAQ and the wiki, to no avail). I'm on Ubuntu server
8.04.1 and Postgres 8.3.7.

Thanks and regards,

Will Temperley

В списке pgsql-general по дате отправления:

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: Information about columns
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Killing a data modifying transaction