pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pg_cancel_backend and pg_terminate_backend
Date: Wed, 19 Apr 2023 22:48:18 +0200
Message-ID: <961aa7e4-b076-c66b-3c23-32bdd5e352a3@jakobs.com> (raw)
In-Reply-To: <CAOC+FBW=KK04qkY6r0ueEX6JnKK4-8u365uuOrf3UM1UrPNbxA@mail.gmail.com>
References: <CAOC+FBVZFVSF1ntpf7UwQ==YA1KaerSrH0_BH+pmczEp88r2Ug@mail.gmail.com>
	<c43689c6-1aa3-9258-09a7-de8046699dc5@gmx.net>
	<CAOC+FBW=KK04qkY6r0ueEX6JnKK4-8u365uuOrf3UM1UrPNbxA@mail.gmail.com>

Am 19.04.23 um 22:13 schrieb Wells Oliver:
> Because longer idle transactions are used by a bunch of processes, but 
> it's a certain group of users I don't want having idle transactions, 
> so here we are...
>
> On Wed, Apr 19, 2023 at 1:11 PM Thomas Kellerer <shammat@gmx.net> wrote:
>
>     Wells Oliver schrieb am 19.04.2023 um 21:41:
>     > 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.
>
>     Why don't you use the idle_in_transaction_session_timeout to do
>     this automatically?
>
Actually, you can set this for certain users:

ALTER ROLE alice SET idle_in_transaction_session_timeout TO '100 s';

But the fact that this is possible implies that each session can set 
this parameter to any value, AFAIK. Correct me if I'm wrong.

-- 

Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012



Attachments:

  [application/pgp-signature] OpenPGP_signature (202B, ../961aa7e4-b076-c66b-3c23-32bdd5e352a3@jakobs.com/3-OpenPGP_signature)
  download

view thread (11+ messages)  latest in thread

Message-ID: <961aa7e4-b076-c66b-3c23-32bdd5e352a3@jakobs.com>
Permalink:  ../961aa7e4-b076-c66b-3c23-32bdd5e352a3@jakobs.com/
Also on:    postgresql.org/message-id/961aa7e4-b076-c66b-3c23-32bdd5e352a3@jakobs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
  Subject: Re: pg_cancel_backend and pg_terminate_backend
  In-Reply-To: <961aa7e4-b076-c66b-3c23-32bdd5e352a3@jakobs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox