Search Results
https://dev.mysql.com/doc/refman/8.4/en/fulltext-stopwords.html
The stopword list is loaded and searched for full-text queries using the server character set and collation (the values of the character_set_server and collation_server system variables). False hits or misses might occur for stopword lookups if the ...
https://dev.mysql.com/doc/refman/8.4/en/gone-away.html
An INSERT or REPLACE statement that inserts a great many rows can also cause these sorts of errors. Either one of these statements sends a single request to the server irrespective of the number of rows to be inserted; thus, you can often avoid the ... This section also covers the related Lost connection to server during query ...
https://dev.mysql.com/doc/refman/8.4/en/grant-tables.html
Note Direct modification of grant tables using statements such as INSERT, UPDATE, or DELETE is discouraged and done at your own risk. The mysql system database includes several grant tables that contain information about user accounts and the ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-ft-index-cache-table.html
The INNODB_FT_INDEX_CACHE table provides token information about newly inserted rows in a FULLTEXT index. The INNODB_FT_INDEX_CACHE table has these columns: WORD A word extracted from the text of a newly inserted row. Before querying it, set the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-and-mysql-replication.html
It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica.
https://dev.mysql.com/doc/refman/8.4/en/innodb-index-types.html
To get the best performance from queries, inserts, and other database operations, it is important to understand how InnoDB uses the clustered index to optimize the common lookup and DML operations. Auto-increment column values are unique and are ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-midpoint_insertion.html
Newly read blocks are inserted into the middle of the LRU list. All newly read pages are inserted at a location that by default is 3/8 from the tail of the LRU list. This arrangement divides the LRU list into two segments, where the pages downstream ... Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-physical-structure.html
When new records are inserted into an InnoDB clustered index, InnoDB tries to leave 1/16 of the page free for future insertions and updates of the index records. If index records are inserted in a sequential order (ascending or descending), the ...
https://dev.mysql.com/doc/refman/8.4/en/memory-storage-engine.html
Deleted rows are put in a linked list and are reused when you insert new data into the table. MEMORY tables also have none of the problems commonly associated with deletes plus inserts in hashed tables. For example, you can put statements such as ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-operations-per-fragment.html
Since NDB does not use single-key access for ordered indexes, the counts for tot_key_reads, tot_key_inserts, tot_key_updates, tot_key_writes, and tot_key_deletes are not incremented by ordered index operations. Note When using tot_key_writes, you ...