summaryrefslogtreecommitdiff
path: root/sql/sql_class.h
diff options
context:
space:
mode:
authorDaniele Sciascia <daniele.sciascia@galeracluster.com>2016-07-14 14:29:59 +0200
committerNirbhay Choubey <nirbhay@mariadb.com>2016-08-10 11:00:15 -0400
commit9a809fe31be15131baf909e898c1ad2c02976728 (patch)
tree742ffb54eccc4ad05db7abed0bdd409d425b246e /sql/sql_class.h
parent38a0def80588dd8a093af3e225101365c74e0faa (diff)
downloadmariadb-git-9a809fe31be15131baf909e898c1ad2c02976728.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.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/sql/sql_class.h b/sql/sql_class.h
index ad3e94d43ca..e42eeacfff0 100644
--- a/sql/sql_class.h
+++ b/sql/sql_class.h
@@ -55,6 +55,7 @@ struct wsrep_thd_shadow {
ulong tx_isolation;
char *db;
size_t db_length;
+ my_hrtime_t user_time;
};
#endif
class Reprepare_observer;