phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Strayer <jstra...@proofpoint.com>
Subject On duplicate key update
Date Mon, 26 Aug 2019 18:51:30 GMT
How does atomic update work with multiple clients?  Assuming that there is no matching record
to begin with the access won’t be locked.  It seems like two threads could write conflicting
data since they both see no existing record (NER).  Is that correct? Or is there something
that will serialize the writes so that only one of them sees the NER state?
Mime
View raw message