Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_cancel_backend and pg_terminate_backend - Mailing list pgsql-admin

From MichaelDBA
Subject Re: pg_cancel_backend and pg_terminate_backend
Date
Msg-id 8d16a5ba-a4bc-f139-5f25-daef5ae85340@sqlexec.com
Whole thread Raw
In response to pg_cancel_backend and pg_terminate_backend  (Wells Oliver <wells.oliver@gmail.com>)
Responses pg_cancel_backend and pg_terminate_backend  ("Wetmore, Matthew (CTR)" <Matthew.Wetmore@express-scripts.com>)
List pgsql-admin
Tree view
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: Wells Oliver
Date:
Subject: pg_cancel_backend and pg_terminate_backend
Next
From: "Wetmore, Matthew (CTR)"
Date:
Subject: pg_cancel_backend and pg_terminate_backend