| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: The documentation for READ COMMITTED may be incomplete or wrong |
| Date: | 2023-05-18 15:22:54 |
| Message-ID: | 3798164.1684423374@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Aleksander Alekseev <aleksander(at)timescale(dot)com> writes:
>> A colleague of mine, Ante Krešić, got puzzled by the following behavior:
> That's not a documentation problem. That's a bug, and an extremely
> nasty one. A quick check shows that it works as expected up through
> v13, but fails as described in v14 and later. Needs bisecting ...
Ugh. Bisecting says it broke at
86dc90056dfdbd9d1b891718d2e5614e3e432f35 is the first bad commit
commit 86dc90056dfdbd9d1b891718d2e5614e3e432f35
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Wed Mar 31 11:52:34 2021 -0400
Rework planning and execution of UPDATE and DELETE.
which was absolutely not supposed to be breaking any concurrent-execution
guarantees. I wonder what we got wrong.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-05-18 15:27:22 | Re: The documentation for READ COMMITTED may be incomplete or wrong |
| Previous Message | Nathan Bossart | 2023-05-18 15:20:18 | Re: The documentation for READ COMMITTED may be incomplete or wrong |