Re: pg_cancel_backend and pg_terminate_backend

From: MichaelDBA <MichaelDBA(at)sqlexec(dot)com>
To: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_cancel_backend and pg_terminate_backend
Date: 2023-04-19 19:46:29
Message-ID: 8d16a5ba-a4bc-f139-5f25-daef5ae85340@sqlexec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

My experience with the older PG versions is that I couldn't stop a query
sometimes with pg_cancel_backend, so I had to resort to
pg_terminate_backend.

Regards,
Michael Vitale

Wells Oliver wrote on 4/19/2023 3:41 PM:
> I usually prefer pg_cancel_backend because it seems.. nicer, but
> lately I've had a troublesome user who leaves transactions open and
> I've scripted up a call to pg_terminate_backend after 60 minutes in an
> idle transaction. It works well.
>
> Question: is there any server impact beyond that user's transaction
> when calling pg_terminate_backend? I feel like there _used_ to be,
> maybe in PG9, where I recall maybe seeing a server disconnect or
> something when using terminate.
>
> Just curious about this approach. Thanks.
>
> --
> Wells Oliver
> wells(dot)oliver(at)gmail(dot)com <mailto:wellsoliver(at)gmail(dot)com>

Regards,

Michael Vitale

Michaeldba(at)sqlexec(dot)com <mailto:michaelvitale(at)sqlexec(dot)com>

703-600-9343

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Wetmore, Matthew (CTR) 2023-04-19 19:51:17 pg_cancel_backend and pg_terminate_backend
Previous Message Wells Oliver 2023-04-19 19:41:54 pg_cancel_backend and pg_terminate_backend