| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Robert Treat <rob(at)xzilla(dot)net>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New docs chapter on Transaction Management and related changes |
| Date: | 2022-11-18 19:33:26 |
| Message-ID: | Y3feBvf5p4g0AVh4@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Nov 13, 2022 at 12:56:30PM +0100, Laurenz Albe wrote:
> > Maybe there's a way to reword the entire phrase that leads to a better
> > formulation of the idea.
>
> Any of your auggestions is better than "unaborted".
>
> How about:
>
> If <literal>AND CHAIN</literal> is specified, a new transaction is
> immediately started with the same transaction characteristics (see <xref
> linkend="sql-set-transaction"/>) as the just finished one.
> This new transaction won't be in the <quote>aborted</quote> state, even
> if the old transaction was aborted.
I think I am going to keep "(unaborted)".
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-11-18 19:34:34 | Re: New docs chapter on Transaction Management and related changes |
| Previous Message | Bruce Momjian | 2022-11-18 19:31:38 | Re: New docs chapter on Transaction Management and related changes |