| 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 |
| Subject: | Re: Document How Commit Handles Aborted Transactions |
| Date: | 2025-08-22 13:17:01 |
| Message-ID: | CALdSSPjmmZSOnZ9PSBifHNEfkt4BmcRk41cJKNfLYLZ0emmECA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 29 May 2025 at 04:32, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> Recent discussion led me to realize we are also contrary to the SQL Standard here. v3 updates the Commit reference page to reflect this fact.
>
> Leaving ready-to-commit.
>
> David J.
>
Hi!
I reviewed your changes and I agree with them.
The only aspect that drew my attention is in the following sentence:
>+ but instead goes into an aborted state. While in this state all commands except
> + <xref linkend="sql-commit"/> and <xref linkend="sql-rollback"/> are ignored
We can also do ABORT;
Is this worth noting?
--
Best regards,
Kirill Reshke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-08-22 13:31:27 | Re: Document How Commit Handles Aborted Transactions |
| Previous Message | Doruk Yilmaz | 2025-08-22 12:51:59 | Re: [Patch] add new parameter to pg_replication_origin_session_setup |