Start Updating a table variable

Updating a table variable

Change buffer: In a memory change buffer is a part of Inno DB buffer pool and on disk, it is part of system tablespace, so even after database restart index changes remain buffered.

This blog post is all about new My SQL 5.7 physical, logical architecture and it’s components.

In this blog post, I will try to explain things in flow including data processing and SQL execution in My SQL with the help of diagrams.

Will discuss more Inno DB, since it’s default and main storage engine for My SQL.

: Contains server_uuid : My SQL Configuration file.

– Data that is being reused is always in the same memory.

– Data that does not use, will get phased out eventually.

Unlike the other databases, My SQL is a very flexible and offers different kinds of storage engines as a plugin for different kinds of needs.

Because of this, My SQL architecture and behavior will also change as per the use of storage engines, for example transactional [Inno DB] and non-transactional [My ISAM] engines data storage and SQL execution methods will be different and within the server it will use engine specific components like memory and buffers depending on type storage engine will get used for the SQL operation.

If an index is large then it will only cache index structure. Storage engine: My SQL component that manages physical data (file management) and locations.

Storage engine responsible for SQL statement execution and fetching data from data files.

–log-error=file_name Log errors and startup messages to this file. Server : My SQL instance where actual data getting stored and data processing is happening.