Bureaucrats, editor, reviewer, Administrators
13,554
edits
Changes
Jump to navigation
Jump to search
no edit summary
The use of the monitor also prevents the system from deadlocks, because the critical resource is only assigned to one writing transaction resp. a group of
reading transactions.
==Locking==
{{Introduced with Version 7.2:}}
==Updates==
During the term of a database update, a locking file {{Mono|upd.basex}} will reside in that database directory. If the update fails for some unexpected reason, or the process is killed ungracefully, this file may not be deleted. In this case, the database cannot be opened anymore using the default commands, and the message "Database ... is being updated, or update was not completed" will be shown instead. If the locking file is manually removed, you may be able to reopen the database, but you should be aware that database may have got corrupt due to the interrupted update process, and you should revert to the most recent database backup.
==Pins==
The standalone versions of BaseX (command-line, GUI) cannot be synchronized with other BaseX instances. If concurrent write operations are to be performed, we generally recommend users to always work with the client/server architecture.
To avoid database corruptions caused by unmanaged concurrent write operations, a process-specific {{Mono|pin...basex}} file will be created in a database directory when a database is opened. When an update operation is triggered, it will be rejected with the message "Database ... is opened by another process." if other pin files are found in the directory.
The same message may appear whenever an unused pin file remains after a client has been ungracefully killed or shut down. In this case, you may manually remove the pin files.
[[Category:Server]]
[[Category:Internals]]
