From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Kenneth Marshall <ktm(at)rice(dot)edu> |
Cc: | Kevin Wilkinson <w(dot)kevin(dot)wilkinson(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Methods to quickly spin up copies of an existing databases |
Date: | 2019-03-01 21:08:36 |
Message-ID: | 87imx2l2uj.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Kenneth Marshall <ktm(at)rice(dot)edu> writes:
> On Fri, Mar 01, 2019 at 11:57:30AM -0800, Kevin Wilkinson wrote:
>
>> if you are able/willing to use ZFS (rather than ext4, xfs, ...) to
>> store your database, then it might work for you. ZFS is
>> copy-on-write so it can very quickly clone a database.
>>
>> kevin
>
> Hi Arjun
>
> Redhat 7 does have LVM snapshots that does something similar. Kevin is
> correct, COW is the secret.
Going a bit further...
Any sort of storage backend that can support *atomic* snapshots across
*all* volumes (in case multiple tablespaces ar involved), can be used to
permit $instantaneous cloning where instantaneous relates to the actual
snapshot time and crash recovery.
Inability to make *atomic* snaps but perhaps seperate snaps very
quickly, combined with PITR can result in clones of high-churn systems
sized in TBs (as in our use case) to be provisioned in about 1 minute.
Nothing but the most trivial system can be cloned rapidly and perhaps
any number of times in succession without employment of
thin-provisioning, copy-on-write (as mentioned already), etc.
Virtual copy is more and more compelling as physical
size, or more precisely, *physical* copy time grow.
HTH
>
> Regards,
> Ken
>
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Klein | 2019-03-01 21:28:35 | Re: Methods to quickly spin up copies of an existing databases |
Previous Message | Stephen Frost | 2019-03-01 21:00:50 | Re: PostgreSQL (linux) configuration with GSSAPI to a Windows domain |