Re: conflict txns in serialization isolation - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: conflict txns in serialization isolation
Date
Msg-id 28391.1090619023@sss.pgh.pa.us
Whole thread Raw
In response to Re: conflict txns in serialization isolation  (Yi LIN <ylin30@cs.mcgill.ca>)
Responses Re: conflict txns in serialization isolation
List pgsql-jdbc
Yi LIN <ylin30@cs.mcgill.ca> writes:
> Read-committed is different from Snapshot in that
> Read-Committed txn will read data committed before read operation starts
> but snapshot txn will read data committed before the whole txn starts.

That's a true statement for SELECT, but a read-committed UPDATE will
in fact find and update the latest version of the row; it won't cause
changes to be lost, even if they occurred after the UPDATE statement as
a whole started.  The same is true of SELECT FOR UPDATE.

I'm not sure how that relates to your previous observations though.
Can you duplicate the apparent misbehavior in psql?  I can't.

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Yi LIN
Date:
Subject: Re: conflict txns in serialization isolation
Next
From: Oliver Jowett
Date:
Subject: Re: JDBC memory usage