diff options
author | Daniele Sciascia <daniele.sciascia@galeracluster.com> | 2016-07-14 14:29:59 +0200 |
---|---|---|
committer | Nirbhay Choubey <nirbhay@mariadb.com> | 2016-07-25 21:37:15 -0400 |
commit | 7431368eafb3e531ba3926e85cc515778f6b5e2f (patch) | |
tree | 8f21c501bcebd6274e6be5a731e8f004b5190133 /sql/sql_class.h | |
parent | cbc8a84fa2e65cad7561fa53799ca0273e8a5ff5 (diff) | |
download | mariadb-git-7431368eafb3e531ba3926e85cc515778f6b5e2f.tar.gz |
MW-292 Reset timestamp after transaction replay
Transaction replay causes the THD to re-apply the replication
events from execution, using the same path appliers do. While
applying the log events, the THD's timestamp is set to the
timestamp of the event.
Setting the timestamp explicitly causes function NOW() to
always the timestamp that was set. To avoid this behavior we
reset the timestamp after replaying is done.
Diffstat (limited to 'sql/sql_class.h')
-rw-r--r-- | sql/sql_class.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sql/sql_class.h b/sql/sql_class.h index 9ee5a40dc99..bf3d043cc1a 100644 --- a/sql/sql_class.h +++ b/sql/sql_class.h @@ -68,6 +68,7 @@ struct wsrep_thd_shadow { ulong tx_isolation; char *db; size_t db_length; + my_hrtime_t user_time; }; #endif class Reprepare_observer; |