On 6/28/2006 12:28 PM, John Sidney-Woollett wrote: > Our data centre suffered a power failure on Friday, and it killed our > time server. > > The clocks on our master and slave databases are now (badly) out of sync!! > > Our master DB is 2 minutes ahead of the actual time > > Our slave database is 2 hours ahead of the master > > Actual: Wed Jun 28 16:21:57 GMT 2006 > > Master: Wed Jun 28 16:23:22 GMT 2006 > > Slave: Wed Jun 28 18:23:12 GMT 2006 > > Can I just rsync the clocks on these two servers, or will it send slony > into a tailspin? > > If I stop the slon processes before resetting the clocks, will I get > away with it? > > I really don't want to have to uninstall the cluster and start it again > (after syncing the clocks). > > Can anyone advise?
Slony-I doesn't use the system time for anything data consistency related. Your sl_status view and some logging might look a bit odd until you adjust the time and all systems caught up to a point where screwed timestamps float through the guts, but that's about it. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] # _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
