Request a Demo
Home   >   mailing lists

Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction - Mailing list pgsql-bugs

From 崔紫玉
Subject Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction
Date
Msg-id 5eba3d4e.22dfa.199ebed21cd.Coremail.cuiziyu20@otcaix.iscas.ac.cn
Whole thread Raw
In response to Re: BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
Hi,

Thank you for your explanation. However, for the UPDATE statement “UPDATE t0 SET c1 = 9, c2 = 9 WHERE c2 = 5;” in
transaction2, 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

pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Next
From: Dmitry Fomin
Date:
Subject: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)