Hi Christian,
I figured it might be ill-advised, just as my reason to do it might be… :)
I’m creating database backups manually because I want to compress them with tar and zstd instead of zip. I also upload them to S3. I was previously creating a backup through BaseX, unzipping it, recompressing it, and then uploading it, but I can achieve the same result in a much faster way by creating and uploading the .tar.zst file by hand. While doing so, I was hoping to lock the database.
As an alternative, I would be happy to contribute code that lets users select how to compress their backups — the .tar.zst approach requires a couple extra dependencies but the compression ratio is worth it for me.
Let me know what you think.
Thanks, Matt
On Wed, Jun 11, 2025 at 4:44 PM Christian Grün christian.gruen@gmail.com wrote:
Hi Matt,
Locking is a low-level mechanism of the database system. It should be avoided to try to influence the behavior from outside.
What would be your reason for (un)locking databases manually?
Best, Christian
Matt Dziuban mrdziuban@gmail.com schrieb am Mi., 11. Juni 2025, 21:55:
Hello everyone,
Is there any function or command I can use to manually lock and unlock a database? Based on the documentation on File-System Locks https://docs.basex.org/12/Transaction_Management#file-system_locks it sounds like maybe just creating an upd.basex file in the database directory would be sufficient?
Thanks in advance, Matt