Re: Document How Commit Handles Aborted Transactions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Ahmed Ashour <a8087027(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Document How Commit Handles Aborted Transactions
Date: 2026-03-26 19:17:39
Message-ID: 1025342.1774552659@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kirill Reshke <reshkekirill(at)gmail(dot)com> writes:
> On Fri, 22 Aug 2025 at 18:31, David G. Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>> Listing commands described as being “present for historical reasons” in the documentation seems unnecessary. We don’t list abort in the “See Also” section either.

> I bumped into specific behaviour of COMMIT in an already-broken
> transaction yet again recently. So, I moved CF entry to the next CF,
> hope this will get eventually merged.
> LGTM

Pushed with minor emendations.

I'm not quite sure why we describe ABORT as quasi-deprecated but not
BEGIN; neither of them are in the standard. I'm disinclined to touch
that state of affairs though.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2026-03-26 19:18:26 Add custom EXPLAIN options support to auto_explain
Previous Message Alvaro Herrera 2026-03-26 19:15:14 Re: Adding REPACK [concurrently]