Donald, It depends on your application and by how much you change the time.
If you have a database field that is populated with the system time when you insert records your application logic may not work as intended. Not sure why you would want to play with the system clock in the first place. If you use NTP (Network Time Protocol) your server will always have the exact time. If your time is off you usually only have to change it once to the correct time. And it is good practice to have the database down if you ever have to set the time backwards. E.g. if my system clock would be 15 minutes to fast, I would keep the database down for at least 15 minutes after chaning the clock back to avoid mismatch in the timestamps. Regards, Nikolaus Dilger On Fri, 21 Feb 2003, "Donald Fraser" wrote: Could somebody tell me the consequences of�setting the date forward in�time on the server running PostgreSQL and then at a later date, after some transactions have been committed,�setting the date back in time? � Thanks in advance, Donald Fraser ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
