Horton
Menu

Re: Document How Commit Handles Aborted Transactions

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kirill Reshke <reshkekirill@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Ahmed Ashour <a8087027@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-26T19:17:39Z
Lists: pgsql-hackers 
Kirill Reshke <reshkekirill@gmail.com> writes:
> On Fri, 22 Aug 2025 at 18:31, David G. Johnston
> <david.g.johnston@gmail.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Doc: commit performs rollback of aborted transactions.