During a background synchronization, the database engine drops the dbmlsync connection to the remote database and rolls back
any uncommitted dbmlsync operations if another connection is waiting for access to any database resource that dbmlsync has
locked. This allows the other connections to go forward without waiting for the synchronization to complete. Depending on
the operations dbmlsync had outstanding when its connection is dropped, there may still be a significant delay for the waiting
connection as the database rolls back the dbmlsync uncommitted changes.