From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Document How Commit Handles Aborted Transactions |
Date: | 2024-12-31 20:49:53 |
Message-ID: | CAKFQuwbanRGokTHQfG99J9xTw09gw=B4fYYW_PYaXKBu--R34g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thoughts?
On Fri, Dec 20, 2024 at 9:02 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> Hi,
>
> The commit reference page lacks an "Outputs" section even though it is
> capable of outputting both "COMMIT" and "ROLLBACK".
>
> The attached adds this section, describes when each applies, and then
> incorporates the same into the main description for commit as well as the
> transaction section of the tutorial - which presently seems to be the main
> discussion area for the topic (the Concurrency Control chapter lacks a
> section for this introductory material).
>
> This was noted as being needed by Tom Lane back into 2006 but it
> never happened.
> https://www.postgresql.org/message-id/28798.1142608067%40sss.pgh.pa.us
>
> It came up again when I was answering a question on Slack regarding
> "commit and chain" wondering whether the "and chain" could be made
> conditional (i.e., could the new transaction start aborted) on
> whether commit outputted "commit" or "rollback".
>
> Its left implied that this behavior of "rollback" is standard-conforming.
> Please feel free to suggest/add language to the Compatibility section if
> this is not the case.
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-12-31 20:52:07 | Re: Backport of CVE-2024-10978 fix to older pgsql versions (11, 9.6, and 9.4) |
Previous Message | David G. Johnston | 2024-12-31 20:49:27 | Re: Improve documentation regarding custom settings, placeholders, and the administrative functions |