[MDEV-777] LP:761603 - Innodb and other errors must cause assertions in debug mode Created: 2011-04-15  Updated: 2014-01-15  Resolved: 2014-01-15

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Philip Stoev (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug761603.xml    

 Description   

Certain errors, in InnoDB and out of it are simply printed to STDOUT. Instead, in a debug build, an assertion should be raised. This will allow such errors to be detected more easily in automated testing, especially since their format is not unified and therefore it is difficult to simply watch the log file during the test. An assertion is much more easier to test, simplfy and debug.

In particular, the following errors have been observed:

InnoDB: Error: row_search_for_mysql() is called without ha_innobase::external_lock()
110415 13:32:28 [ERROR] trx->active_flag & TRX_ACTIVE_IN_MYSQL== 0, but trx->conc_state != TRX_NOT_STARTED

so please convert:

  • All errors that look like those two (that is, transaction and handler related) and
  • All errors printed inside innodb regardless of the actual text


 Comments   
Comment by Rasmus Johansson (Inactive) [ 2011-09-05 ]

Launchpad bug id: 761603

Comment by Elena Stepanova [ 2013-03-27 ]

It's a feature request, not a bug, moving to Tasks.

Generated at Thu Feb 08 06:31:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.