Skip navigation links

MySQL Forums :: Replication :: measuring slave lag without sysdate() - 4.1.13


Advanced Search

Re: measuring slave lag without sysdate() - 4.1.13
Posted by: wildcat crazy ()
Date: February 09, 2012 02:08PM

http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html#function_sysdate reveals that this did infact change with 5.0.12.

"As of MySQL 5.0.12, SYSDATE() returns the time at which it executes. This differs from the behavior for NOW(), which returns a constant time that indicates the time at which the statement began to execute...

In addition, the SET TIMESTAMP statement affects the value returned by NOW() but not by SYSDATE(). This means that timestamp settings in the binary log have no effect on invocations of SYSDATE()."

In versions before this, the SET TIMESTAMP *DOES* affect SYSDATE(), so on the slave the INSERT or UPDATE will ALWAYS show the same time as the Master. Always.

Hence my problem.

So, any creative ways of determining this without using SYSDATE()?

thanks.

Options: ReplyQuote


Subject Views Written By Posted
measuring slave lag without sysdate() - 4.1.13 1448 wildcat crazy 02/07/2012 05:54AM
Re: measuring slave lag without sysdate() - 4.1.13 522 Rick James 02/08/2012 02:09AM
Re: measuring slave lag without sysdate() - 4.1.13 675 wildcat crazy 02/08/2012 04:26AM
Re: measuring slave lag without sysdate() - 4.1.13 570 Rick James 02/09/2012 11:05AM
Re: measuring slave lag without sysdate() - 4.1.13 831 wildcat crazy 02/09/2012 02:08PM
Re: measuring slave lag without sysdate() - 4.1.13 399 Rick James 02/11/2012 12:00AM
Re: measuring slave lag without sysdate() - 4.1.13 441 Baron Schwartz 02/20/2012 06:25AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.