On Mon, Sep 12, 2016 at 3:46 PM, Lee Hachadoorian
wrote:
> * 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
Just update one copy, then send pg_dump's to the others for stomping
over the ol
On 09/12/2016 02:35 PM, Lee Hachadoorian wrote:
On Mon, Sep 12, 2016 at 5:12 PM, Adrian Klaver
wrote:
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
On Mon, Sep 12, 2016 at 5:12 PM, Adrian Klaver
wrote:
> 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 u
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 con
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 in
