On Fri, Dec 5, 2008 at 11:25 PM, Glyn Astill <[EMAIL PROTECTED]> wrote:
>
> select pg_cancel_backend();
No, pg_cancel_backend() cancels only *query*, and doesn't kill idle
in transaction. I think that killing the backend (idle in transaction) with
SIGTERM is better way.
Regards,
--
Fujii Masao
>>
>> Could anyone tell me what's the best thing to with idle
>> transactions
>> that are holding locks?
On Fri, Dec 5, 2008 at 2:25 PM, Glyn Astill <[EMAIL PROTECTED]> wrote:
>
> select pg_cancel_backend();
>
Thanks. Sorry for the basic question.
Will
--
Sent via pgsql-general mailing list (p
select pg_cancel_backend();
--- On Fri, 5/12/08, William Temperley <[EMAIL PROTECTED]> wrote:
> From: William Temperley <[EMAIL PROTECTED]>
> Subject: [GENERAL] in transaction - safest way to kill
> To: pgsql-general@postgresql.org
> Date: Friday, 5 December, 2008, 2:0
Hi all
Could anyone tell me what's the best thing to with idle transactions
that are holding locks?
I just killed the process as I wanted to get on with some work. I'm
just not sure this is a good idea when we go into production.
Cheers
Will T
--
Sent via pgsql-general mailing list (pgsql-gen
