From: Stephen Frost <sfrost@snowman.net>
To: Keith <keith@keithf4.com>
Cc: drum.lucas@gmail.com <drum.lucas@gmail.com>
Cc: Scott Whitney <scott@journyx.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Incremental Refresh - PostgreSQL 9.2
Date: Wed, 24 Feb 2016 13:10:04 -0500
Message-ID: <20160224181004.GH3127@tamriel.snowman.net> (raw)
In-Reply-To: <CAHw75vu9hPUp6ACaizxUGAY1J96JdKLXdjeK37LiBLAUrZbJmw@mail.gmail.com>
References: <CAE_gQfUqvmewj91Sg81Orc7S+=aO0xG-xftMB4UycByVEdWHZw@mail.gmail.com>
<CAKFQuwYFoEwQOXwvOuiqx40mJb+T2P3LKKXcTJNKGsX0M+LZ=w@mail.gmail.com>
<e0121fj0w32l77ofwjfb14i2.1456267414369@email.android.com>
<CAE_gQfXJx81wGXRYEO2jUTLTLkvkWvCiE6bRUxjQAOG08zPVGQ@mail.gmail.com>
<ewwmlvageqrkn3rdthfso2nq.1456277100577@email.android.com>
<CAE_gQfVqK3VZzQGUnK0aQd55VmQVRGQ3c2v4vQ=NXuQjotUM-w@mail.gmail.com>
<CAE_gQfUb90_aD3643SLNT7fMO4z+43auVp7nN7Sb7g7zrTKO5g@mail.gmail.com>
<CAHw75vu9hPUp6ACaizxUGAY1J96JdKLXdjeK37LiBLAUrZbJmw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Keith,
* Keith (keith@keithf4.com) wrote:
> However, once you restore that backup and bring it up as a standalone
> database instance, you can no longer use the WAL stream from the original
> instance to "replay" those changes. This is also the case with any sort of
> rsync'ing of the data files from one instance to another.
Right, but if you don't mind throwing away the changes which were made
to the restored server (the test server) then you can use rsync (if the
source database is shut down) to re-sync the restored server without
having to re-copy everything (I'd strongly recommend using the CRC
option to rsync). The same is possible with pgBackRest, which allows
you to keep the source database online (pgBackRest will check that the
hashes match between the backup and the restored system when doing
incremental restores, there's no need to explicitly ask for that as
there is with rsync).
> You may be better off looking into a logical replication solution to copy
> your data to a testing system if it needs to be a standalone system. That
> is not currently built into Postgres, but it's on track for possible
> inclusion with 9.6. In the mean time look into tools such as Mimeo or
> Bucardo.
>
> https://github.com/omniti-labs/mimeo
> https://bucardo.org/wiki/Bucardo
Right, and there's also Slony. These are useful if the requirement is
that changes to the test/restored server be persisted.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sfrost@snowman.net, keith@keithf4.com, drum.lucas@gmail.com, scott@journyx.com, david.g.johnston@gmail.com
Subject: Re: Incremental Refresh - PostgreSQL 9.2
In-Reply-To: <20160224181004.GH3127@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox