mariadb/innobase/trx
Timothy Smith fd5642b67d Applying InnoDB snashot 5.0-ss4007, part 2. Fixes
Bug #18828: If InnoDB runs out of undo slots, it returns misleading 'table is full'

This is a backport of code already in 5.1+.  The error message change referred
to in the detailed revision comments is still pending.

Detailed revision comments:

r3937 | calvin | 2009-01-15 03:11:56 +0200 (Thu, 15 Jan 2009) | 17 lines
branches/5.0:

Backport the fix for Bug#18828. Return DB_TOO_MANY_CONCURRENT_TRXS
when we run out of UNDO slots in the rollback segment. The backport
is requested by MySQL under bug#41529 - Safe handling of InnoDB running
out of undo log slots.

This is a partial fix since the MySQL error code requested to properly
report the error condition back to the client has not yet materialized.
Currently we have #ifdef'd the error code translation in ha_innodb.cc.
This will have to be changed as and when MySQl add the new requested
code or an equivalent code that we can then use.

Given the above, currently we will get the old behavior, not the
"fixed" and intended behavior.

Approved by:	Heikki (on IM)
2009-03-02 17:57:09 -07:00
..
Makefile.am my_strtoll10-x86.s: 2006-12-31 01:02:27 +01:00
trx0purge.c trx0undo.c, trx0purge.c: 2004-11-21 17:38:15 +02:00
trx0rec.c Applying InnoDB snashot 5.0-ss4007, part 2. Fixes 2009-03-02 17:57:09 -07:00
trx0roll.c This ChangeSet must be null-merged to 5.1. 2006-12-18 18:41:38 -07:00
trx0rseg.c Backport innodb_max_purge_lag from 4.1 2004-10-27 13:33:11 +03:00
trx0sys.c Fix for bug #13367, post-review changes 2005-09-27 13:37:20 +04:00
trx0trx.c Cherry-pick InnoDB fixes for Bug#34286, Bug#35352, and Bug#36600 from snapshot 2008-07-31 15:47:57 -06:00
trx0undo.c Applying InnoDB snashot 5.0-ss4007, part 2. Fixes 2009-03-02 17:57:09 -07:00