From: | Lee Hachadoorian <Lee(dot)Hachadoorian+L(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Replication Recommendation |
Date: | 2016-09-12 19:46:33 |
Message-ID: | CANnCtn+wFqAJKb2aqPwAyNZGpNqCGb5N8APOcwufc+01FS2B2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Regards,
--Lee
--
Lee Hachadoorian
Assistant Professor of Instruction, Geography and Urban Studies
Assistant Director, Professional Science Master's in GIS
Temple University
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2016-09-12 20:01:44 | Re: Predicting query runtime |
Previous Message | Merlin Moncure | 2016-09-12 18:16:16 | Re: Predicting query runtime |