On Mon, Feb 20, 2017 at 07:27:34PM +0000, Rakesh Kumar wrote: > I tested it and it works. what I did was to select xmin and xmax and then > sleep for a min. > In the meantime, I update the same row in another session. > After 1 min the update session failed to update any row because the > combination of xmin > and xmax was no longer true. > > I was under the impression that xmin/xmax can not be used in the where clause > for business logic as described above. > > Am I missing anything ? If this works, it can make optimistic locking lot > easier due to generic coding using xmin/xmax.
Works fine. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
