This straight from issue is in the howto_install document.  
It is good to know it is not important, but the document should be
changed, too.

--elein

On Tue, Sep 07, 2004 at 05:31:36PM -0400, Jan Wieck wrote:
> On 9/7/2004 5:09 PM, elein wrote:
> 
> >The danger is when the slon processes are running
> >and the replications are earlier than the replicator.
> >
> >If you are rebooting, temporary out of sync clocks
> >should not be a problem if you perform a proper shutdown.
> 
> Ooops, didn't see that. Sorry Elein.
> 
> Slony doesn't use timestamps at all. So the system clocks are totally 
> irrelevant for the replication system to work. So the clocks can differ 
> by a week or be in sync to the millisecond, it doesn't make the 
> slightest difference to the data.
> 
> The usefullness of the debug output, telling you how long specific steps 
> took, will be screwed and bogus. But that's all.
> 
> 
> Jan
> 
> >
> >--elein
> >
> >
> >On Tue, Sep 07, 2004 at 02:37:34PM -0600, Ed L. wrote:
> >>On Tuesday September 7 2004 2:09, elein wrote:
> >>> A very basic how to article is now available in
> >>> the latest issue of GeneralBits:
> >>> http://www.varlena.com/GeneralBits/
> >>>
> >>> Comments and Corrections are always welcome.
> >>
> >>"The Real Time Clocks of the servers hosting the nodes must be in sync."
> >>
> >>How important is this?  What happens if the clocks are temporarily out of 
> >>sync?  Say, for example, on a reboot?  
> >>
> >>Ed
> >>
> >_______________________________________________
> >Slony1-general mailing list
> >Slony1-general at gborg.postgresql.org
> >http://gborg.postgresql.org/mailman/listinfo/slony1-general
> 
> 
> -- 
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me.                                  #
> #================================================== JanWieck at Yahoo.com #