| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | 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-02-17 08:17:17 |
| Message-ID: | CALdSSPhRtZvY0DNtiwtcNXyvmBzAhMtgzqNK_Ecfdms21c88rg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 22 Aug 2025 at 18:31, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Friday, August 22, 2025, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>>
>>
>> We can also do ABORT;
>>
>
> 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.
>
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2026-02-17 08:20:44 | Re: Our ABI diff infrastructure ignores enum SysCacheIdentifier |
| Previous Message | Andrei Lepikhov | 2026-02-17 08:09:30 | Re: Add into REFRESH PUBLICATION parameter exception_behaviour |