Database Lab 0.3: users can choose which “thin clone manager” to use, ZFS or LVM
*Update: see the discussion on Hacker News!*
Version 0.3 of Database Lab (with a minor update to 0.3.1) adds support of LVM as an alternative to ZFS to enable thin cloning of large databases. This was one of the most requested features after the initial launch of the public Database Lab version a month ago.
LVM can be chosen as a “thin-clone manager” instead of ZFS for those who do not want to use ZFS and prefer staying on more popular file systems (ext4, xfs) in non-production environments. It is worth noting that ZFS remains the default and recommended option. Postgres.ai team is very satisfied with the experience of using it running Database Labs for multi-terabyte, heavily loaded databases.
Compared to ZFS, the LVM module has a certain restriction: it is not possible to support multiple snapshots and allow choosing the snapshot when requesting a new clone. With LVM, the new clones always are based on the latest state of the database.
We invite everyone to test both modules, join our Community Slack, and provide your feedback! See the links below.
- What is Database Lab
- Database Lab tutorial for using Database Lab with ZFS
- Database Lab tutorial for using Database Lab with LVM
- Please support the project giving a GitLab star: https://gitlab.com/postgres-ai/database-lab
- Join our Community Slack to discuss Database Lab and share your feedback with us
- Source code and issue tracker
- Changelog and release notes