From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Incremental Refresh - PostgreSQL 9.2 |
Date: | 2016-02-24 16:31:19 |
Message-ID: | 20160224163119.GG3127@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
David,
* David G. Johnston (david(dot)g(dot)johnston(at)gmail(dot)com) wrote:
> On Tue, Feb 23, 2016 at 2:59 PM, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)com>
> wrote:
> > Question:
> > Now that the test server has a full copy from master, how could I just do
> > a incremental refreshing once a month?
> >
> > Instead copying all the DB (1.7GB), just copy what has been changed?
> > Is that possible?
> >
> >
> You cannot accomplish incremental updates if your choice of tool is
> pg_dump.
Agreed.
> The only way to do a true incremental would be to rely upon
> something like rsync on the data directory while the master server is
> offline.
pgBackRest actually provides incremental backups and restores and I've
used it for exactly this kind of setup previously.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2016-02-24 18:10:04 | Re: Incremental Refresh - PostgreSQL 9.2 |
Previous Message | Matheus de Oliveira | 2016-02-24 10:56:00 | Re: Incremental Refresh - PostgreSQL 9.2 |