GLB 0.7.3 released

in

Featuring bugfixes and cleanups. Notably now connects/disconnects can happen concurrently. Download here

Kommentit

How galera supports "SELECT

How galera supports "SELECT FOR UPDATE" statement for pessimistic locking?

SELECT FOR UPDATE

Galera is concerned only with committed changes so it is simply does not care about "SELECT FOR UPDATE". Note however, that if a writeset from another node needs to modify any row locked by local transaction, that transaction is rolled back as deadlocked. This is true of any locks, including those left by "SELECT FOR UPDATE". Thus in Galera cluster application may have deadlocks where in a single server setup it normally didn't and "SELECT FOR UPDATE" is no guarantee for successful commit.