Re: Using SAN Splits to instantly copy a DB

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Using SAN Splits to instantly copy a DB
Date: 2006-11-15 20:28:43
Message-ID: 20061115202843.GB31020@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 15, 2006 at 01:41:47PM -0600, Ron Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/15/06 09:47, Jim Nasby wrote:
> > On Nov 14, 2006, at 3:44 PM, Paul Silveira wrote:
> [snip]
> > Rule 2 is needed to ensure that the data files in the database are all
> > consistent to each other. If you have a SAN/filesystem with snapshot
> > capability (sounds like you do), then you can do that to create the copy
> > rather than shutting the database down.
>
> How does SAN-snapshot ensure transactional consistency?

There is write-ahead logging to do that. It's the same machanism used
to ensure database consistancy after a crash. When you take a snapshot
and start a new postmaster on the snapshot, it sees what looks like a
crashed database and recovers it to the instant it snapshotted (aka
"crashed").

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2006-11-15 20:34:20 Re: Using SAN Splits to instantly copy a DB
Previous Message Martijn van Oosterhout 2006-11-15 20:24:18 Re: PgSQL not recognized