Home  >  Article  >  Database  >  Recommend 10 commonly used usage tables

Recommend 10 commonly used usage tables

伊谢尔伦
伊谢尔伦Original
2017-06-15 13:34:201406browse

When looking at the max_binlog_stmt_cache_size parameter explanation, there is such a sentence. If nontransactional statements within a transaction require more than this many bytes of memory, the server generates an error. So, what are nontransactional statements? Look for the nontransactional keyword at http://dev.mysql.com/, and the first one that comes out is Rollback Failure for Nontransactional Tables. So what are Nontransactional Tables? Nontransactional Tables, non-transactional tables, tables that do not support transactions, that is, tables that use the MyISAM storage engine. Characteristics of non-transaction tables

1. MySQL transaction tables and non-transaction tables

Recommend 10 commonly used usage tables

##Introduction: When viewing the max_binlog_stmt_cache_size parameter explanation, there is such a sentence: If nontransactional statements within a transaction require more than this many bytes of memory, the server generates an error.

2. MySQL large data volume rapid insertion method and statement optimization sharing

Introduction: For transaction tables, BEGIN and COMMIT should be used instead of LOCK TABLES to speed up insertion

3. undo series learning Oracle IMU and Redo Private Strands technology

Recommend 10 commonly used usage tables

Introduction: In the traditional undo management model, Oracle treats undo and data block equally. This will roughly have three disadvantages: 1) When the transaction starts, the segment header storing the transaction table is not in the memory

4. Mysql main desynchronization problem handling

Recommend 10 commonly used usage tables

Introduction: Due to various reasons, data inconsistency often occurs in the mysql master-slave architecture, which can be roughly summarized as follows: Category 1: Write data to standby database 2: Execute non-deterministic query3: Roll back transactions that mix transaction tables and non-transaction tables 4

5. Mysql non-transaction table rollback Failure phenomenon

#Introduction: When executing ROLLBACK (rollback), if you receive the following message, it means that one or more tables used in the transaction do not support the transaction: Warning: Some changes to non-transactional tables cannot be rolled back. These non-transactional tables are not affected by ROLLBACK statements. If you accidentally mixed transactional and non-transactional tables in a transaction, the most likely cause of this message is that you thought this

6. Oracle block cleanout

Introduction: To put it simply, there are active transaction marks on Oracle blocks. If a transaction is committed, some blocks have been written back to the datafile before the commit. , or if the transaction affects too many blocks, then only the transaction table information in the undo segment header will be cleared during commit, and the transaction flag on the data block will not be cleared. Otherwise, the code will be cleared.

7. Detailed Explanation of Oracle Transaction Table Experiment

Introduction: There is a very important piece of information in the rollback segment header, which is the transaction table. Frequent access to transaction tables may cause contention for rollback segment headers. Understanding what operations access transaction tables is important to understanding the cause of rollback segment header contention. Let's do some experiments to verify what kind of operations will access the transaction table. First, a brief introduction to a view

8. Interpretation of REDORECORD format generated by DML statements in IMU mode

Introduction: Summary: The REDO RECORD formula generated by the DML statement in IMU mode is that there is an operating change rector first, then a change rector that writes transaction information to the transaction table in the UNDO segment header, and then after the operating change rector is submitted, processing is performed. The data is placed in UNDO's change rector before modification. Note: In the experiment, INSERT and DELETE are done one after another, UPDAT

9. Mysql master-slave synchronization problem handling

Recommend 10 commonly used usage tables

Introduction: Due to various reasons, data inconsistency often occurs in the mysql master-slave architecture, which can be roughly summarized into the following categories 1: Backup Library writing data 2: Execute non-deterministic query 3: Roll back transactions that mix transaction tables and non-transaction tables 4: Binlog or relaylog data corruption and data out-of-synchronization can cause fatal harm to applications. When the master-slave number appears

10. MySQL Advanced Features----Transaction Processing_MySQL

Introduction: To use transaction processing in MySQL , first you need to create a table using a transactional table type (such as BDB = Berkeley DB or InnoDB). CREATE TABLE account (account_id BIGINT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT, balance DOUBLE) TYPE = InnoDB; To use transaction processing on a transaction table, you must first close the self

The above is the detailed content of Recommend 10 commonly used usage tables. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn