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:38:25 |
Message-ID: | Y3ffMf96pDmMeXPe@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 18, 2022 at 02:33:26PM -0500, Bruce Momjian wrote:
> 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)".
Attached is the most current version of the patch.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
Attachment | Content-Type | Size |
---|---|---|
xact.diff | text/x-diff | 24.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2022-11-18 20:25:36 | Re: Reducing power consumption on idle servers |
Previous Message | Bruce Momjian | 2022-11-18 19:37:39 | Re: New docs chapter on Transaction Management and related changes |