You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-5Lines changed: 7 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,8 @@ To discuss Database Lab, try a demo, or ask any questions,
40
40
41
41
**TL;DR:** you need:
42
42
- any machine with a separate disk that is big enough to store a single copy of your database,
43
-
- Linux with Docker and ZFS,
43
+
- Linux with Docker,
44
+
- ZFS to enable thin cloning (the default option; also, LVM is supported as an alternative),
44
45
- initial copy of your Postgres database.
45
46
46
47
Details:
@@ -55,10 +56,11 @@ use pg_basebackup, restoration from an archive (such as WAL-G, Barman, pgBackRes
55
56
supported for RDS, until AWS guys decide to allow replication connections),
56
57
- upon request, Database Lab will do "thin cloning" of PGDATA, providing fully independent writable
57
58
Postgres clones to users;
58
-
- currently, the only technology supported for thin cloning is ZFS,
59
-
so [ZFS on Linux](https://zfsonlinux.org/) needs to be installed on the machine,
60
-
- however, it is easy to extend and add, say, LVM or Ceph - please write us if you
61
-
need it; also, contributions are highly welcome).
59
+
- currently, two technologies are supported for thin cloning:
60
+
- ZFS: [ZFS on Linux](https://zfsonlinux.org/) needs to be installed on the machine,
61
+
- LVM: with [LVM](https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)), all thin clones will be based on the latest version of the database (with ZFS, you can have multiple snapshots prepared and choose which one to use when requesting a new thin clone).
62
+
- it is easy to extend and add, Ceph - please contact us if you need it;
63
+
- comments, bug reports, and contributions are highly welcome.
0 commit comments