\u3053\u3093\u306b\u3061\u308f\u3002\u305b\u3058\u307e\u3067\u3059\u3002\u4eca\u56de\u3082 replication \u306e\u8a71\u3092\u3057\u307e\u3059\u3002<\/p>\n
\u7b2c\u4e8c\u56de\u3067\u3059\u3002<\/p>\n
\u4eca\u56de\u306e\u4e3b\u306a\u304a\u984c\u306f\u3001 THD::decide_logging_format() \u3068\u3044\u3046\u95a2\u6570\u306b\u306a\u308a\u307e\u3059\u3002 THD::decide_logging_format() \u306e\u4ed5\u69d8\u304c\u308f\u304b\u308b\u3068\u3001binlog_format \u304c\u539f\u56e0\u3067 replication \u6b62\u307e\u308b\u7406\u7531\u304c\u3001\uff08\u305d\u3053\u305d\u3053\uff09\u308f\u304b\u308b\u3088\u3046\u306b\u306a\u308b\u3067\u3057\u3087\u3046\u3002<\/p>\n
\u307e\u305f\u3001Row-Based Replication \u306b\u79fb\u884c\u3057\u305f\u3068\u304d\u3001 THD::decide_logging_format() \u4ee5\u5916\u3067 replication \u304c\u505c\u6b62\u3057\u3066\u3057\u307e\u3046\u30b1\u30fc\u30b9\u306a\u3069\u306b\u3064\u3044\u3066\u3082\u3001\u8efd\u304f\u30e1\u30e2\u7a0b\u5ea6\u306b\u66f8\u3044\u3066\u304a\u304d\u307e\u3059\u3002<\/p>\n
\uff08MySQL Internals \u306f\u5fae\u5999\u306b\u5185\u5bb9\u304c\u53e4\u304b\u3063\u305f\u308a\u3059\u308b\u3093\u3067\u3059\u304c\uff09\u3001\u53c2\u8003\u307e\u3067\u306b\u3001\u307e\u305a\u306f 19.4.1 Determining the Logging Format<\/a> \u3092\u8aad\u3093\u3067\u307f\u307e\u3057\u3087\u3046\u3002<\/p>\n \n At parse time, it is detected if the statement is unsafe to log in statement format (that is, requires row format). If this is the case, the THD::Lex::set_stmt_unsafe() function is called. This must be done prior to the call to THD::decide_logging_format() (that is, prior to lock_tables). As a special case, some types of unsafeness are detected inside THD::decide_logging_format(), before the logging format is decided. Note that statements shall be marked unsafe even if binlog_format!=mixed.\n<\/p><\/blockquote>\n \u6b21\u306f\u3001\u5177\u4f53\u7684\u306b\u3001 SQLCOM_UPDATE \u53d7\u3051\u305f\u3068\u3053\u308d\u304b\u3089\u3001 THD::decide_logging_format() \u3092\u898b\u3066\u3044\u304d\u307e\u3057\u3087\u3046\u3002\u4eca\u56de\u3082 MySQL 8.0.12 \u306e\u30bd\u30fc\u30b9\u30b3\u30fc\u30c9\u3092\u30d9\u30fc\u30b9\u306b\u8aad\u3093\u3067\u3044\u304d\u307e\u3059\u3002<\/p>\n \u3053\u3093\u306a\u304b\u3093\u3058\u3067 statement \u3092\u5b9f\u884c\u3059\u308b\u524d\u306b\u3044\u3063\u305f\u3093 lock_tables() \u3092\u5b9f\u884c\u3057\u3066\u304a\u308a\u307e\u3057\u3066<\/p>\n lock_tables() \u306e\u4e2d\u3067 THD::decide_logging_format() \u304c\u547c\u3070\u308c\u3066\u3044\u307e\u3059\u3002<\/p>\n https:\/\/github.com\/mysql\/mysql-server\/blob\/mysql-8.0.12\/sql\/sql_base.cc#L6436<\/a><\/p>\n THD::decide_logging_format() \u3068\u3044\u3046\u95a2\u6570\u306b\u3064\u3044\u3066\u3067\u3059\u304c\u3001\u30b3\u30e1\u30f3\u30c8<\/a>\u304c\u3051\u3063\u3053\u3046\u5145\u5b9f\u3057\u3066\u3044\u307e\u3059\u3002<\/p>\n \u3056\u3063\u304f\u308a\u307e\u3068\u3081\u306f\u30b3\u30e1\u30f3\u30c8\u306e\u3068\u304a\u308a\u3067<\/p>\n Row Injection \u3068\u3044\u3046\u306e\u306f\u3001 binlog_format=ROW \u306b\u3057\u305f\u3068\u304d binlog \u306b\u51fa\u529b\u3055\u308c\u308b\u3001UPDATE_ROWS_EVENT \u306a\u3069\u306e\u3053\u3068\u3067\u3057\u3087\u3046\u306d\u3002\u305d\u308c\u3089\u3092 SQL_Thread \u306a\u3069\u3067\u5b9f\u884c\u3059\u308b\u5834\u5408\u304c Statement Type = I \u306b\u306a\u308a\u307e\u3059\u3002<\/p>\n \u3067\u306f\u3001\u9806\u3092\u8ffd\u3063\u3066\u898b\u3066\u3044\u304d\u307e\u3057\u3087\u3046\u3002<\/p>\n Row capable \u3067\u3082 Stmt capable \u3067\u3082\u306a\u3044 storage engine \u306e\u4f8b\u306e\u4e00\u3064\u306f\u3001 performance schema \u3067\u3059\u3002<\/p>\n https:\/\/github.com\/mysql\/mysql-server\/blob\/mysql-8.0.12\/storage\/perfschema\/ha_perfschema.h#L73-L97<\/a><\/p>\n \u300c\u9593\u9055\u3063\u3066\u3082 replication \u3067\u304d\u308b\u3068\u601d\u3046\u306a\u3088\uff1f\u300d\u3068\u3044\u3046\u3053\u3068\u3067\u3057\u3087\u3046\u3002<\/p>\n Stmt capable \u3067\u3042\u308a Row capable \u3067\u306a\u3044 storage engine \u3067\u3059\u304c\u3001\u30bd\u30fc\u30b9\u30b3\u30fc\u30c9\u4e0a\u3067\u306f\u30c6\u30b9\u30c8\u306e\u305f\u3081\u306b \u5b58\u5728\u3057\u3066\u3044\u308b\u3088\u3046\u3067\u3059\u3002 \u306a\u306e\u3067\u3001\u3053\u308c\u306f\u3044\u3063\u305f\u3093\u5fd8\u308c\u3066\u3082\u826f\u3044\u3067\u3057\u3087\u3046\u3002<\/p>\n https:\/\/github.com\/mysql\/mysql-server\/blob\/mysql-8.0.12\/storage\/example\/ha_example.h#L100<\/a><\/p>\n Row capable \u3067\u3042\u308a Stmt capable \u3067\u306a\u3044 storage engine \u3067\u3059\u304c\u3001\u8eab\u8fd1\u306a\u3068\u3053\u308d\u3067\u3044\u3046\u3068\u3001 READ COMMITTED or READ UNCOMMITTED \u306a InnoDB \u304c\u8a72\u5f53\u3057\u307e\u3059\u3002InnoDB \u304c Stmt capable \u3067\u3042\u308b\u306e\u306f\u3001 Isolation level \u304c REPEATABLE READ \u304b SERIALIZABLE \u306e\u3068\u304d\u306b\u9650\u3089\u308c\u308b\u308f\u3051\u3067\u3059\u3002<\/p>\n \u3068\u3044\u3063\u305f\u3053\u3068\u3092\u8e0f\u307e\u3048\u308b\u3068\u3001\u60f3\u5b9a\u3059\u3079\u304d\u73fe\u5b9f\u7684\u306a Decision table for logging format \u306f\u3001\u6b21\u306e\u3088\u3046\u306a\u3082\u306e\u3067\u3057\u3087\u3046\u3002<\/p>\n\n
\/*\n Locking of tables is done after preparation but before optimization.\n This allows to do better partition pruning and avoid locking unused\n partitions. As a consequence, in such a case, prepare stage can rely only\n on metadata about tables used and not data from them.\n *\/\n if (!is_empty_query()) {\n if (lock_tables(thd, lex->query_tables, lex->table_count, 0)) goto err;\n }\n\n \/\/ Perform statement-specific execution\n if (execute_inner(thd)) goto err;<\/pre>\n\n
Decision table for logging format\n ---------------------------------\n\n The following table summarizes how the format and generated\n warning\/error depends on the tables' capabilities, the statement\n type, and the current binlog_format.\n\n Row capable N NNNNNNNNN YYYYYYYYY YYYYYYYYY\n Statement capable N YYYYYYYYY NNNNNNNNN YYYYYYYYY\n\n Statement type * SSSUUUIII SSSUUUIII SSSUUUIII\n\n binlog_format * SMRSMRSMR SMRSMRSMR SMRSMRSMR\n\n Logged format - SS-S----- -RR-RR-RR SRRSRR-RR\n Warning\/Error 1 --2732444 5--5--6-- ---7--6--\n\n Legend\n ------\n\n Row capable: N - Some table not row-capable, Y - All tables row-capable\n Stmt capable: N - Some table not stmt-capable, Y - All tables stmt-capable\n Statement type: (S)afe, (U)nsafe, or Row (I)njection\n binlog_format: (S)TATEMENT, (M)IXED, or (R)OW\n Logged format: (S)tatement or (R)ow\n Warning\/Error: Warnings and error messages are as follows:\n\n 1. Error: Cannot execute statement: binlogging impossible since both\n row-incapable engines and statement-incapable engines are\n involved.\n\n 2. Error: Cannot execute statement: binlogging impossible since\n BINLOG_FORMAT = ROW and at least one table uses a storage engine\n limited to statement-logging.\n\n 3. Error: Cannot execute statement: binlogging of unsafe statement\n is impossible when storage engine is limited to statement-logging\n and BINLOG_FORMAT = MIXED.\n\n 4. Error: Cannot execute row injection: binlogging impossible since\n at least one table uses a storage engine limited to\n statement-logging.\n\n 5. Error: Cannot execute statement: binlogging impossible since\n BINLOG_FORMAT = STATEMENT and at least one table uses a storage\n engine limited to row-logging.\n\n 6. Error: Cannot execute row injection: binlogging impossible since\n BINLOG_FORMAT = STATEMENT.\n\n 7. Warning: Unsafe statement binlogged in statement format since\n BINLOG_FORMAT = STATEMENT.\n\n In addition, we can produce the following error (not depending on\n the variables of the decision diagram):\n\n 8. Error: Cannot execute statement: binlogging impossible since more\n than one engine is involved and at least one engine is\n self-logging.\n\n 9. Error: Do not allow users to modify a gtid_executed table\n explicitly by a XA transaction.\n\n For each error case above, the statement is prevented from being\n logged, we report an error, and roll back the statement. For\n warnings, we set the thd->binlog_flags variable: the warning will be\n printed only if the statement is successfully logged.<\/code><\/pre>\n return HA_NO_TRANSACTIONS | HA_NO_AUTO_INCREMENT |\n HA_PRIMARY_KEY_REQUIRED_FOR_DELETE | HA_NULL_IN_KEY |\n HA_NULL_PART_KEY;<\/code><\/pre>\n \/** @brief\n This is a list of flags that indicate what functionality the storage engine\n implements. The current table flags are documented in handler.h\n *\/\n ulonglong table_flags() const {\n \/*\n We are saying that this engine is just statement capable to have\n an engine that can only handle statement-based logging. This is\n used in testing.\n *\/\n return HA_BINLOG_STMT_CAPABLE;\n }<\/code><\/pre>\n\n
handler::Table_flags ha_innobase::table_flags() const {\n THD *thd = ha_thd();\n handler::Table_flags flags = m_int_table_flags;\n\n \/* If querying the table flags when no table_share is given,\n then we must check if the table to be created\/checked is partitioned.\n *\/\n if (table_share == NULL && thd_get_work_part_info(thd) != NULL) {\n \/* Currently ha_innopart does not support\n all InnoDB features such as GEOMETRY, FULLTEXT etc. *\/\n flags &= ~(HA_INNOPART_DISABLED_TABLE_FLAGS);\n }\n\n \/* Temporary table provides accurate record count *\/\n if (table_share != NULL &&\n table_share->table_category == TABLE_CATEGORY_TEMPORARY) {\n flags |= HA_STATS_RECORDS_IS_EXACT;\n }\n\n \/* Need to use tx_isolation here since table flags is (also)\n called before prebuilt is inited. *\/\n\n ulong const tx_isolation = thd_tx_isolation(thd);\n\n if (tx_isolation <= ISO_READ_COMMITTED) {\n return (flags);\n }\n\n return (flags | HA_BINLOG_STMT_CAPABLE);\n}<\/code><\/pre>\n\n