Re: [PATCH] Add prepared_orphaned_transaction_timeout GUC

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Nikhil Chawla <chawlanikhil24(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Add prepared_orphaned_transaction_timeout GUC
Date: 2026-03-25 09:06:22
Message-ID: 2DCDBFFC-4B03-4EBC-88A3-06AD29933F17@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 23 Mar 2026, at 16:47, Nikhil Chawla <chawlanikhil24(at)gmail(dot)com> 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-03-25 09:12:18 Re: SQL Property Graph Queries (SQL/PGQ)
Previous Message Jim Jones 2026-03-25 09:05:22 Re: VACUUM FULL, CLUSTER, and REPACK block on other sessions' temp tables