public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nikhil Chawla <[email protected]>
To: Andrey Borodin <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] Add prepared_orphaned_transaction_timeout GUC
Date: Thu, 26 Mar 2026 13:02:23 +0530
Message-ID: <CAAXajwD5pT+BtQqLTn=6DDs8NAWgqm4S6esSn0Zr3Ev1kVbYPg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAXajwDOvTwLQ=rO5hOKsR_VTikST1rN-moO46YhYEgsO00dqg@mail.gmail.com>
	<[email protected]>

Hi Andrey,

My purview is absolutely influenced from "long running transactions" which
are essentially killed by pg itself through idle_session_timeout. This also
happens when the user sets an acceptable value to this timeout and the user
is aware that transactions can be killed if threshold is exceeded, which
further can be confirmed through logs.

The same analogy is being applied with orphaned prepared transactions,
which may/may not complete ever , but going to hinder autovacuum,
increasing bloat. When user sets the value, user will be aware that the
prepared transactions can disappear automatically.



On Wed, Mar 25, 2026 at 2:36 PM Andrey Borodin <[email protected]> wrote:

>
>
> > On 23 Mar 2026, at 16:47, Nikhil Chawla <[email protected]>
> wrote:
> >
> > idle_in_transaction_session_timeout, idle_session_timeout,
> statement_timeout, but no equivalent for prepared transactions
>
> During implementation of the transaction_timeout we briefly considered
> prepared xacts, but decided that it's a footgun.
>
> DBA can easily do the same with a cron job, but in case of prepared
> transactions monitoring is crucial. Prepared xacts are used to coordinate
> commit in many durable systems and orphan prepared xact is evidence of
> serious malfunction.
>
> Silent rollback in any scenario I can imagine is a disaster.
>
>
> Best regards, Andrey Borodin.



-- 
Regards,
Nikhil Chawla
Twitter <https://twitter.com/chawlanikhil24; | LinkedIn
<http://linkedin.com/in/chawlanikhil24;

view thread (4+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [PATCH] Add prepared_orphaned_transaction_timeout GUC
  In-Reply-To: <CAAXajwD5pT+BtQqLTn=6DDs8NAWgqm4S6esSn0Zr3Ev1kVbYPg@mail.gmail.com>

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

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