diff options
| author | unknown <elliot@mysql.com> | 2006-03-17 10:25:29 +0100 |
|---|---|---|
| committer | unknown <elliot@mysql.com> | 2006-03-17 10:25:29 +0100 |
| commit | 367442f754a97d87077c99bc5805b41da5ac7119 (patch) | |
| tree | 2d7f0581fad7174f6de58be991ec71eca3a1892f /configure.in | |
| parent | fd6d45f0b0de5a8f0767d96d8f12cbca649f454c (diff) | |
| download | mariadb-git-367442f754a97d87077c99bc5805b41da5ac7119.tar.gz | |
BUG#18283 When InnoDB returns error 'lock table full', MySQL can write
to binlog too much.
When InnoDB has to rollback a transaction because the lock table has
filled up, it also needs to inform the upper layer that the transaction
was rolled back so that the cached transaction is not written to the
binary log.
sql/ha_innodb.cc:
When InnoDB rolls back a transaction in HA_ERR_LOCK_TABLE_FULL, it
needs to inform the upper layer to rollback the transaction also.
Diffstat (limited to 'configure.in')
0 files changed, 0 insertions, 0 deletions