On 8/9/2019 11:00 AM, Olivier Mascia wrote:
A connection holds a SHARED lock. It did start a DEFERRED transaction then read something. Now it executes COMMIT. Will the lock be upgraded from SHARED to EXCLUSIVE for the very short duration of the COMMIT (the connection made no writing, as evidenced by its SHARED lock), or will this specific case elude upgrading the lock and simply exit the transaction, releasing the SHARED-lock to NO lock?
It must be the latter, otherwise readers won't be able to get out in the presence of RESERVED or PENDING lock from a prospective writer. You'd have deadlocks all the time. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
