Re: Replication Recommendation - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Replication Recommendation
Date
Msg-id aea5f204-e6a0-25b2-c5d1-63b2ee69cbcb@aklaver.com
Whole thread Raw
In response to Replication Recommendation  (Lee Hachadoorian <Lee.Hachadoorian+L@gmail.com>)
Responses Re: Replication Recommendation
List pgsql-general
On 09/12/2016 12:46 PM, Lee Hachadoorian wrote:
> There are a wide variety of Postgres replication solutions, and I
> would like advice on which one would be appropriate to my use case.
>
> * Small (~half dozen) distributed workforce using a file sharing
> service, but without access to direct network connection over the
> internet
> * Database is updated infrequently, when new government agency data
> releases replace old data
> * Because database is updated infrequently, workforce can come
> together for LAN-based replication as needed
> * Entire database is on the order of a few GB
>
> Given this, I am considering the super lowtech "replication" solution
> of updating "master" and doing a full database drop and restore on the
> "slaves". But I would like to know which of the other (real)
> replication solutions might work for this use case.

If I follow correctly the layout is?:

        Main database <--- Govt. data
                    |
                         |
                        \ /

           File share
                         |
                         |
                        \ /

DB       DB        DB       DB       DB        DB

User 1   User 2    User 3   User 4   User 5    User 6



For your simple scenario you might want to look at:

https://www.postgresql.org/docs/9.5/static/app-pgbasebackup.html


>
> Regards,
> --Lee
>


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2
Next
From: Istvan Soos
Date:
Subject: Re: Predicting query runtime