MySQL Bugs: #39743: create_time and update_time keep updating in archive table without any activity

Bug #39743	create_time and update_time keep updating in archive table without any activity
Submitted:	30 Sep 2008 1:21	Modified:	1 Nov 2008 15:01
Reporter:	Chris Dempsey	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Archive storage engine	Severity:	S3 (Non-critical)
Version:	5.0.22	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
I have several hundred small (3MB) tables which are stored in the Archive format as they are read-only, and it saves several gigabytes of disk space. A routine runs each night looking for old table to delete, but "show table status" keeps showing the tables as being fresh and new.

How to repeat:
archive table created, then show table status run with a small delay between each command. Results are as attached

"show table status" queries and results on archive table

Attachment: archive_updates.txt (text/plain), 4.06 KiB.

Thank you for a problem report. Please, try to repeat with a newer version, 5.0.67, and inform about the results.

This is on a live server, but can try on the development server, will advise when it is complete and tested again.

In the meantime, I checked the files this morning, and saw this:
----------------------------------------------------------------
-bash-3.00$ ls -al 1356046.*
-rw-rw----  1 mysql mysql      19 Oct  1 08:45 1356046.ARM
-rw-rw----  1 mysql mysql 3276907 Oct  1 08:45 1356046.ARZ
-rw-rw----  1 mysql mysql    9042 Sep 30 13:57 1356046.frm
-bash-3.00$
----------------------------------------------------------------
so the 'data' is being touched by something. I also note the 'Data_length' is increasing by small amounts (about 20 bytes) each time it's updates itself too. No activity (reading or writing) has been done to this table since it was created.

Please, inform about any findings with 5.0.67.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".