sorry, half asleep and typing rubbish. --all you need to do is switch master and slave so that "master" is the one box you are currently on
On 9 August 2013 15:35, Bèrto ëd Sèra <berto.d.s...@gmail.com> wrote: > if it's only you using it, all you need to do is switch master and server > so that "server" is the one box you are currently on. If both boxes produce > data at the same time you need a lot of work to manage row versioning. > > > On 9 August 2013 15:27, Paula Kirsch <pl.kir...@gmail.com> wrote: > >> 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 a >> copy running on a linux server. >> >> The development and analysis work often generates corrections on the >> field data input and 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. >> >> (I have also posted this question to pgsql-admin) >> >> Paula >> > > > > -- > ============================== > If Pac-Man had affected us as kids, we'd all be running around in a > darkened room munching pills and listening to repetitive music. > -- ============================== If Pac-Man had affected us as kids, we'd all be running around in a darkened room munching pills and listening to repetitive music.
