Re: Document How Commit Handles Aborted Transactions - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: Document How Commit Handles Aborted Transactions
Date
Msg-id CALdSSPhRtZvY0DNtiwtcNXyvmBzAhMtgzqNK_Ecfdms21c88rg@mail.gmail.com
Whole thread Raw
In response to Re: Document How Commit Handles Aborted Transactions  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Document How Commit Handles Aborted Transactions
List pgsql-hackers
On Fri, 22 Aug 2025 at 18:31, David G. Johnston
<david.g.johnston@gmail.com> wrote:
>
> On Friday, August 22, 2025, Kirill Reshke <reshkekirill@gmail.com> wrote:
>>
>>
>> We can also do ABORT;
>>
>
> Listing commands described as being “present for historical reasons” in the documentation seems unnecessary.  We
don’tlist abort in the “See Also” section either. 
>
> David J.
>

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

--
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: Add into REFRESH PUBLICATION parameter exception_behaviour
Next
From: Andreas Karlsson
Date:
Subject: Re: Our ABI diff infrastructure ignores enum SysCacheIdentifier