Hello Greg, Thanks, that sounds really reasonable. I'll have to get really familiar with it, though. First of all, I need Windows clients for offline use -- maybe cygwin will do. Second, I don't exactly know what is the effect of disabling triggers and rules: will it affect transactions running in parallel (a real problem), or will triggers be disabled for that transaction only (sounds like trouble)? On Fri, Jul 31, 2009 at 8:00 PM, Greg Sabino Mullane<greg@xxxxxxxxxxxx> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > >> - Way of handling conflicting records >> e.g. client A goes offline, client B modifies master, client A >> modifies locally, and when goes online again cannot commit the >> changes. > > One possible solution you should look at is Bucardo, which > does master-master replication. One of the tricky parts you > might want to reconsider though is: > >> The difference is that I do not know when will the client go offline, >> even client does not know (e.g. ISP goes down) and, of course, there >> may be a lot of connections while client is offline. > > This says to me that you should simply make all writes go to the > local box, and have Bucardo keep trying to keep things in sync. > If it can connect, great. If not, it dies and tries again later. > > http://bucardo.org/ > > - -- > Greg Sabino Mullane greg@xxxxxxxxxxxx > End Point Corporation > PGP Key: 0x14964AC8 200907311359 > http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 > -----BEGIN PGP SIGNATURE----- > > iEYEAREDAAYFAkpzMSsACgkQvJuQZxSWSsgpoQCgrNa9PFxtVvKcljTguCCvmN6E > HnkAn3OzYFCJZeR7vvhC9Hr/+DVs9tir > =+Tr0 > -----END PGP SIGNATURE----- > > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > -- G. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
