Re: pg_cancel_backend and pg_terminate_backend - Mailing list pgsql-admin

From Wells Oliver
Subject Re: pg_cancel_backend and pg_terminate_backend
Date
Msg-id CAOC+FBV30ewu-E5T2wwFB17zu2+d4GbPcDGV4nnpqgwVDms=ow@mail.gmail.com
Whole thread Raw
In response to pg_cancel_backend and pg_terminate_backend  ("Wetmore, Matthew (CTR)" <Matthew.Wetmore@express-scripts.com>)
List pgsql-admin
Correct. Is there broader risk to the running server and other connections if a given user's backend is terminated?

On Wed, Apr 19, 2023 at 12:51 PM Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com> wrote:

pg_cancel_backend()

A function which cancels a backend's current query

 

pg_terminate_backend()

A function which instructs a backend to terminate

 

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

 

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.

 

--



--

pgsql-admin by date:

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