From: 崔紫玉 <cuiziyu20@otcaix.iscas.ac.cn>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
Date: Thu, 16 Oct 2025 15:30:10 +0800 (GMT+08:00)
Message-ID: <5eba3d4e.22dfa.199ebed21cd.Coremail.cuiziyu20@otcaix.iscas.ac.cn> (raw)
In-Reply-To: <3080220.1760030272@sss.pgh.pa.us>
References: <19081-3745d3e571c420de@postgresql.org>
<3080220.1760030272@sss.pgh.pa.us>
Hi,
Thank you for your explanation. However, for the UPDATE statement “UPDATE t0 SET c1 = 9, c2 = 9 WHERE c2 = 5;” in transaction 2, why does the UPDATE statement in transaction 2 in the first case fail to match the row that was changed to (5, 5) in the committed transaction 1? In the second case, why does the UPDATE statement in transaction 2 report an error “could not serialize access due to concurrent update”?
Best regards,
Ziyu Cui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: cuiziyu20@otcaix.iscas.ac.cn, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
In-Reply-To: <5eba3d4e.22dfa.199ebed21cd.Coremail.cuiziyu20@otcaix.iscas.ac.cn>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox