MySQL Storage engine Archive

MySQL commonly used engine MyISAM and InnoDB, the former Insert Fast query fast, the latter modification of fast support transactions, each has advantages and disadvantages, in the internet suddenly saw an engine called archive, and quite special

This engine only allows insertions and queries, and does not allow for modification and deletion. Equivalent to having read-only and Write permissions, no modify permissions, and delete permissions. It suddenly occurred to me that this kind of thing is a bit like the slave library in master-detail synchronization, but it has write permission, and it is rather special.

In some fixed dead configurations, this table can be used to eliminate the programmer or the operation of the wrong operation or attempt to modify. The security of the data is fundamentally ensured. Of course, because the times change too fast, demand logic and so on is always changing, this fixed thing is likely to be the unprecedented overthrow and impact, when it really needs to change how to do??

You can try to change the table engine to the InnoDB engine first, and then change the change to the archive engine, the problem is not to use the index, including the primary key ID, etc., this table is used to store things or good.

Here's a summary of what others are doing with this engine.

File system Storage Features: Compression of table data with zlib, less disk I/O data stored in arz suffix files Archiv storage engine features only insert and select operations (row-level and buffer support) can achieve high concurrency of the insert) only allowed on the self-Increment ID column index archive table is about 75% smaller than the MyISAM table, which is about 83% smaller than the InnoDB table that supports transactions. When the amount of data is very large, archive performance will be better than MyISAM. Is the performance of the archive table likely to exceed MyISAM? The answer is yes. According to the MySQL engineer, when the data in the table reaches the magnitude of 1.5GB, and the CPU is relatively fast, the performance of the archive table will go beyond the MyISAM table. Because of this time, the CPU will replace the I/O subsystem as a performance bottleneck. Don't forget that the archive table performs fewer physical I/O operations than any other type of table. A smaller footprint can also work when you are porting MySQL data. When you need to transfer data from one MySQL server to another, the archive table can be easily ported to the new MySQL environment, and you can simply copy the underlying file that saved the archive table to the past. The way of the Sea Thief Link: https://www.jianshu.com/p/c18d4da0a827 Source: Jane Letters Book Copyright belongs to the author, any form of reprint please contact the author to obtain authorization and indicate the source.

Too lazy to knock, just quote someone else's words.

MySQL Storage engine Archive