pg_cancel_backend and pg_terminate_backend - Mailing list pgsql-admin

From Wetmore, Matthew (CTR)
Subject pg_cancel_backend and pg_terminate_backend
Date
Msg-id d10305f0ea744c7c9d279ca327d8d9fb@express-scripts.com
Whole thread Raw
In response to Re: pg_cancel_backend and pg_terminate_backend  (MichaelDBA <MichaelDBA@sqlexec.com>)
List pgsql-admin

You had to be a SU in 8.0, 9.0 allowed you to cancel your own query.

 

From: MichaelDBA <MichaelDBA@sqlexec.com>
Sent: Wednesday, April 19, 2023 2:46 PM
To: Wells Oliver <wells.oliver@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: [EXTERNAL] Re: pg_cancel_backend and pg_terminate_backend

 

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.

 

--

 



Regards,

Michael Vitale

Michaeldba@sqlexec.com

703-600-9343

 

Attachment

pgsql-admin by date:

Previous
From: "Wetmore, Matthew (CTR)"
Date:
Subject: pg_cancel_backend and pg_terminate_backend
Next
From: Wells Oliver
Date:
Subject: Re: pg_cancel_backend and pg_terminate_backend