Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction

From: 崔紫玉 <cuiziyu20(at)otcaix(dot)iscas(dot)ac(dot)cn>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
Date: 2025-10-16 07:30:10
Message-ID: 5eba3d4e.22dfa.199ebed21cd.Coremail.cuiziyu20@otcaix.iscas.ac.cn
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Fomin 2025-10-16 09:46:26 Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
Previous Message Amit Langote 2025-10-16 05:04:17 Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade