Commit 2985ec2d authored by Sergei Golubchik's avatar Sergei Golubchik

add a forgotten debug sync point, that a test case was referring to

parent 937ae82a
...@@ -13,7 +13,7 @@ INSERT INTO t1(k) VALUES (1), (2), (3) ON DUPLICATE KEY UPDATE c='1'; ...@@ -13,7 +13,7 @@ INSERT INTO t1(k) VALUES (1), (2), (3) ON DUPLICATE KEY UPDATE c='1';
# #
# Connection 2 # Connection 2
# #
SET DEBUG_SYNC='start_ha_write_row WAIT_FOR continue2'; SET DEBUG_SYNC='ha_write_row_start WAIT_FOR continue2';
affected rows: 0 affected rows: 0
SET DEBUG_SYNC='after_mysql_insert SIGNAL continue1'; SET DEBUG_SYNC='after_mysql_insert SIGNAL continue1';
affected rows: 0 affected rows: 0
......
...@@ -33,7 +33,7 @@ SET DEBUG_SYNC='ha_write_row_end SIGNAL continue2 WAIT_FOR continue1'; ...@@ -33,7 +33,7 @@ SET DEBUG_SYNC='ha_write_row_end SIGNAL continue2 WAIT_FOR continue1';
--echo # --echo #
--echo # Connection 2 --echo # Connection 2
--echo # --echo #
SET DEBUG_SYNC='start_ha_write_row WAIT_FOR continue2'; SET DEBUG_SYNC='ha_write_row_start WAIT_FOR continue2';
SET DEBUG_SYNC='after_mysql_insert SIGNAL continue1'; SET DEBUG_SYNC='after_mysql_insert SIGNAL continue1';
INSERT INTO t1(k) VALUES (2), (4), (5) ON DUPLICATE KEY UPDATE c='2'; INSERT INTO t1(k) VALUES (2), (4), (5) ON DUPLICATE KEY UPDATE c='2';
......
...@@ -5335,6 +5335,7 @@ int handler::ha_write_row(uchar *buf) ...@@ -5335,6 +5335,7 @@ int handler::ha_write_row(uchar *buf)
int error; int error;
Log_func *log_func= Write_rows_log_event::binlog_row_logging_function; Log_func *log_func= Write_rows_log_event::binlog_row_logging_function;
DBUG_ENTER("handler::ha_write_row"); DBUG_ENTER("handler::ha_write_row");
DEBUG_SYNC_C("ha_write_row_start");
/* If we have a timestamp column, update it to the current time */ /* If we have a timestamp column, update it to the current time */
if (table->timestamp_field_type & TIMESTAMP_AUTO_SET_ON_INSERT) if (table->timestamp_field_type & TIMESTAMP_AUTO_SET_ON_INSERT)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment