From: | Paula Kirsch <pl(dot)kirsch(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | bi-directional syncing suggestions request |
Date: | 2013-08-09 04:25:03 |
Message-ID: | CAHaXFPKRAk7B-qRHZjecpyV-UXQ+A8OBG9ZtA+SH9eRxLj=zmA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi. I'm looking for suggestions for the best solution to the following
situation.
I have a database roughly 300 meg with 30 tables.
For fieldwork, a copy is running on my mac laptop where I can pull up
information and add new entries.
The data analysis and further development is done back at the office on
copy running on a linux server. The development and analysis work
occasionally results in schema changes.
As a result, the situation is bi-directional, so not a master-slave
replication situation and I'm not a professional dba. It is my personal
research data, so I don't have to worry about other users.
My question is whether there is any recommended best practice for
bi-directional syncing (schema changes would only be one direction, but
data entries could flow both ways)?
Any suggestions would be appreciated.
Paula
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2013-08-09 07:27:44 | Re: After upgrading from 9.1.1 to 9.1.9, pgadmin's server status window gives error |
Previous Message | Bruce Momjian | 2013-08-09 01:36:35 | Re: Clarification when using Continous Archiving in 8.4 |