Yeah, why not flush them to disk on a clean shutdown, and periodically before that?
> -----Original Message----- > From: Dotan Cohen [mailto:dotanco...@gmail.com] > Sent: Sunday, June 23, 2013 10:39 AM > To: mysql. > Subject: UPDATE_TIME for InnoDB in MySQL 5.7 > > The MySQL 5.7 changelog mentions: > "Beginning with MySQL 5.7.2, UPDATE_TIME displays a timestamp value for > the last UPDATE, INSERT, or DELETE performed on InnoDB tables. > Previously, UPDATE_TIME displayed a NULL value for InnoDB tables. For > MVCC, the timestamp value reflects the COMMIT time, which is considered > the last update time. Timestamps are not persisted when the server is > restarted or when the table is evicted from the InnoDB data dictionary > cache." > > This is great news! However, I would in fact need the UPDATE_TIME to > persist across database server resets. Is this feature being considered or > discussed? Where might I find it online? > > Thank you to the MySQL team and to Oracle for filling in InnoDB;s missing > features! > > -- > Dotan Cohen > > http://gibberish.co.il > http://what-is-what.com > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql
