The time zones are correct. Besides, the difference is not an even hour, and it varies. Sometimes the master server shows an update_time that is only a few minutes different, other times it is 510 seconds or 633 seconds or 6056 seconds different. Eventually it catches up, but it sometimes takes an hour or two. Other times it catches up immediately after an update. I cannot discern a pattern. The only thing I know is that update_time seems to match the .MYD file's timestamp in Windows.
-- Eric Robinson -----Original Message----- From: Mikael Fridh [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 8:15 PM To: Robinson, Eric Cc: mysql@lists.mysql.com Subject: Re: SHOW TABLE STATUS: Update_Time Is Wrong? Robinson, Eric wrote: > When I execute SHOW TABLE STATUS on my master replication server, it > shows an Update_Time for some tables that is more than 2 hours earlier > than the Update_Time for the same tables on the slave server. However > the bin log names, positions, and number or records are correct. > > What's with that? Let us know if your timezones are set correctly. -- ___ |K | Ongame E-Solutions AB - www.ongame.com | /\| Mikael Fridh / Technical Operations |_\/| tel: +46 18 606 538 / fax: +46 18 694 411 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
