Mon Jan 14 11:50:47 PST 2008
- Previous message: [Slony1-general] URGENT: Migration of master node locked my database
- Next message: [Slony1-general] URGENT: Migration of master node locked my database
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2008-01-14 at 10:56 -0800, Craig James wrote: > Andrew Sullivan wrote: > > On Sat, Jan 12, 2008 at 05:51:57PM -0800, Jeff Frost wrote: > >> You might check the slon logs for any indication this is what caused your > >> problem. I thought slon did its work based entirely on xxid, but I could > >> be wrong. Perhaps one of the developers will comment. In any event, I'm > >> sure you know the clocks should be in sync as a best practice. > > > > Not entirely based on xxid, no. They can't be synced across nodes. You > > _must_ be nntp-synced between your nodes. They should peer from one > > another, and _then_ get their time from some other source. > > I want to be sure I understand this: Are you saying that a few milliseconds of time skew between servers will make Slony fail? > No, it won't. There is always going to be some minor skew, even when synced with NTP. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.
- Previous message: [Slony1-general] URGENT: Migration of master node locked my database
- Next message: [Slony1-general] URGENT: Migration of master node locked my database
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list