lp:~maria-captains/maria/5.5-hf

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

4408. By Alexey Botchkov on 2015-01-15

MDEV-7462 SET STATEMENT .. FOR <DML or DDL> is not recognized as DML or DDL.

4407. By Alexey Botchkov on 2015-01-15

MDEV-7461 Server audit: Queries from executable comments aren't recognized as DDL or DML.

4406. By Alexey Botchkov on 2015-01-15

MDEV-7460 Server audit: (SELECT ...) is not recognized as DML.

4405. By Alexey Botchkov on 2015-01-15

MDEV-7466 Server audit: LOAD XML is not recognized as DML.

4404. By Alexey Botchkov on 2015-01-15

MDEV-7443 Server audit: If both QUERY_DML and QUERY_DDL are set, nothing is logged.

4403. By Alexey Botchkov on 2015-01-14

MDEV-7459 Server audit: Plugin info should be updated.

4402. By Alexey Botchkov on 2015-01-14

MDEV-7443 Server audit: If both QUERY_DML and QUERY_DDL are set, nothing is logged.

4401. By Alexey Botchkov on 2015-01-14

MDEV-7456 Server audit: Empty password in CHANGE MASTER is not obfuscated.

4400. By Alexey Botchkov on 2015-01-09

Audit-plugin v 1.2.0.

4399. By Kristian Nielsen on 2015-01-06

MDEV-7189: main.processlist fails sporadically in buildbot

The test case tried to trigger a DEBUG_SYNC point at the end of a SELECT
SLEEP(5) statement. It did this by using EXECUTE 2, intending to trigger first
at the end of SET DEBUG_SYNC, and second at the end of the SELECT SLEEP(5).

However, in --ps-protocol mode, this does not work, because the SELECT is
executed in two steps (Prepare followed by Execute). Thus, the DEBUG_SYNC got
triggered too early, during the Prepare stage rather than Execute, and the
test case could race and information_schema.processlist see the thread in the
wrong state.

This patch fixes by changing the way the DEBUG_SYNC point is triggered. Now we
add a DBUG injection inside the code for SLEEP(5). This ensures that the
DEBUG_SYNC point is not activated until the SLEEP(5) is running, ensuring
that the following wait for completion will be effective.