| From: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
|---|---|
| To: | Scott Whitney <scott(at)journyx(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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 00:45:59 |
| Message-ID: | CAE_gQfXJx81wGXRYEO2jUTLTLkvkWvCiE6bRUxjQAOG08zPVGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 24 February 2016 at 11:42, Scott Whitney <scott(at)journyx(dot)com> wrote:
> Are you using it for just select queries, or is this a full 100% test
> (insert/update/delete) test environment?
>
> I have both. In my case they are geographically separate. Production
> server at data center. Replicated "just in case," also at data center. At
> HQ, I replicate that for DR purposes. INTERNALLY (gigabit backend), I have
> another internal test server that I refresh FROM THE REPLICATED SERVER AT
> HQ on a regular basis. I use the replicated server to query stuff (select)
> and dump databases to the interaction test server regularly for full
> testing.
>
>
>
That's what I'm looking for:
https://coderwall.com/p/jxebnw/incremental-backups-for-postgresql
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Whitney | 2016-02-24 01:23:40 | Re: Incremental Refresh - PostgreSQL 9.2 |
| Previous Message | Scott Whitney | 2016-02-23 22:42:14 | Re: Incremental Refresh - PostgreSQL 9.2 |