| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | mark maker <mark(at)makr(dot)zone> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Documentation should state what happens, when a commit fails |
| Date: | 2025-05-28 14:59:10 |
| Message-ID: | CAKFQuwYATsj3cY6gOu_yWxcm4qSEspNvmVm=nvXmYBs0vseHzw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, May 28, 2025 at 7:47 AM mark maker <mark(at)makr(dot)zone> wrote:
> Wow, great improvement, thanks!
>
> The "tutorial-transactions" opens a new question that might be useful to
> know: when a transaction enters the aborted state at an early point in time
> (as has now become clear), does this mean it will also relinquish any locks
> and predicate locks early, or will it still hold onto those until
> explicitly rolled back by command?
>
I suppose if the system knows there are no savepoints in progress it could
release the locks and whatnot...not sure if it knows that and acts upon
that knowledge if it does. Easy enough to test with two psql sessions if
you want to give it a go before I or someone else gets around to it.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2025-05-28 15:09:41 | Re: Documentation should state what happens, when a commit fails |
| Previous Message | mark maker | 2025-05-28 14:47:25 | RE: Documentation should state what happens, when a commit fails |