Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Categories: connectors experimental galera main
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

connectors experimental galera main
fce77042914f...
fce77042914f093dfd45ae8bbaeac76e65597b9c
Sergei Petrunia
MDEV-39368: Trace replay: add --extra-server support, part 1.
fbee9164b5ea...
fbee9164b5ea40fc33111f708a559f63494cdb82
Michael Widenius
MDEV-32745 Add a simple MySQL to MariaDB upgrade helper

The tool is named mariadb-migrate-config-file.
The main purpose of the tool is to change MySQL option
files to work both for MySQL and MariaDB.
There are options to do the changes in the options file inline,
or at-end-of-file. One can also remove or comment unknown options.

The list of supported options is generated compile time from
mariadbd --help. All server options, including compiled plugins, are
supported.

The bulk of the code comes from Väinö.
Monty has updated it with a lot of extra options.
Wlad helped with cmake integration

Other things:
- Fixed a memory leak in sql_plugin.cc
- plugin-load will now in case of errors try to load all given plugins
  before aborted
- If silent-startup is used, plugin-load will not give errors for
  plugins it cannot load or warnings about plugin marturity level.
- my_rm_tree() will now delete symlinks, not the actual file, if
  MY_NOSYMLINK flag is used.
- my_stat() will now give data for symlink if MY_NOSYMLINKS is used.
- Added 'number of lines' option to mysqltest --cat_file

@Authors: Väinö Mäkelä <[email protected]>,[email protected]
f9d69306ae19...
f9d69306ae19c6b7ba3b053efe43e1a6b9f09214
Sergei Petrunia
MDEV-39382: Trace replay produces "Impossible WHERE noticed after reading const tables"

Constant table check in make_join_statistics() checks the value of
"table->file->stats.records", not table->used_stat_records. These
two values can be different.

So, make the Optimizer Context save and restore both values.
(used_stat_records was saved already, this patch also saves
table->file->stats.records).
e773d6291a73...
e773d6291a732b3d1a9af9da70c2c3ef2891b0b4
Raghunandan Bhat
MDEV-37491: Assertion `(mem_root->flags & 4) == 0` failed in `void *alloc_root(MEM_ROOT *, size_t)`

Problem:
  Server crashes when a procedure with default parameter is executed and
  default value for the parameter is evaluated after the procedure's
  first execution. For example:

  CREATE PROCEDURE p(x INT DEFAULT (SELECT 1)) ...
  CALL p(1); -- first exec, marks mem_root read-only
  CALL p(); -- tries to allocate on locked when executing DEFAULT

Fix:
  Temporarily clear the read-only flag on the statement memory root to
  allow the allocation. Also adds a debug hook to verify allocation
  happens not more than once per prepared statement and per internal
  table added to the list.
e6d65d6c064d...
e6d65d6c064d5468b03bdedfea9f09796615781f
Raghunandan Bhat
MDEV-37243: SP memory root protection disappears after a metadata change

Problem:
  When a stored routine involes a cursor and metadata of table on which
  the cursor is defined changes, the SP instruction has to be reparsed.
  For ex:
  CREATE OR REPLACE TABLE t1 (a INT);

  CREATE OR REPLACE FUNCTION f1() RETURNS INT
  BEGIN
    DECLARE vc INT DEFAULT 0;
    DECLARE cur CURSOR FOR SELECT a FROM t1;
    OPEN cur;
    FETCH cur INTO vc;
    CLOSE cur;
    RETURN vc;
  END;

  SELECT f1(); - first execution, sp-mem_root marked read-only on exec
  SELECT f1(); - read-only sp-mem_root
  ALTER TABLE t1 MODIFY a TEXT; - metadta change
  SELECT f1(); - reparse, rerun instr and mark new mem_root read-only

  sp_lex_instr is re-parsed after the metadata change, which sets up a
  new mem_root for reparsing. Once the instruction is re-parsed and
  re-executed(via reset_lex_and_exec_core), the new memory root assigned
  to the instruction being reparsed remains writable. This violates the
  invariant of SP memory root protection.

Fix:
  Mark the new memory root created for reparsing with read-only flag,
  after the first execution of the SP instruction.
e214e4e4666e...
e214e4e4666ececf2d1d203c065c7aac9215f7ee
Marko Mäkelä
MDEV-39264: Improve the documentation of ER_CHECKREAD

Similar to ER_LOCK_DEADLOCK and ER_LOCK_WAIT_TIMEOUT, let the ER_CHECKREAD
message suggest that the transaction needs to be restarted. When this error
is reported by InnoDB (only if innodb_snapshot_isolation=ON),
the transaction will be rolled back.
da821d497d48...
da821d497d486fac26b4f2f101c675642f398ed0
PranavKTiwari
MDEV-39245- Check that plugin name is pure ASCII
Fixed - __attribute__ not supported on Windows MSVC
d411e180e289...
d411e180e2890524a8600e6b9da17fdc81678a0e
Sergei Petrunia
MDEV-39368: Make --replay-server[-manual] save the output of last EXPLAIN in the replay.

The last command is set "optimizer_replay_context=null"...
d3767f9649a2...
d3767f9649a21a6478e8e784805f894497b93eaa
Raghunandan Bhat
MDEV-39356: Server crashes when executing `UPDATE ... FOR PORTION OF` with a normal table

Problem:
  Executing an `UPDATE ... FOR PORTION OF` statement on a table without
  a defined period results in assertion failure. The code in
  `SELECT_LEX::period_setup_conds` attempts to compare a NULL
  period name identifier using `streq()`, which triggers the assertion
  in `strnncoll` funtion.

Fix:
  Replace `streq` with `streq_safe` in `SELECT_LEX::period_setup_conds`
  to handle NULL pointers safely via an early-exit.
c79060ad79cd...
c79060ad79cd286559fd3a9bb2ea6f2e069b42ef
Abhishek Bansal
MDEV-38474: ASAN heap-use-after-free in st_select_lex_unit::cleanup

cleanup_stranded_units() was added at the start of
st_select_lex_unit::cleanup() by 34a8209d6657. This causes a
use-after-free when nested subqueries are merged into their parent
unit. With nested subqueries like:

  SELECT * FROM t1
  WHERE a IN (SELECT b FROM t2
              WHERE a IN (SELECT c FROM t3 WHERE FALSE HAVING c < 0));

the stranded_clean_list chains the units as: Unit1 -> Unit2 -> Unit3.
Because cleanup_stranded_units() was called first, Unit1->cleanup()
would recursively trigger Unit2->cleanup(), which in turn would
trigger Unit3->cleanup(). Unit3's cleanup frees its heap-allocated
join structures. But since Unit3 was merged into Unit2, Unit2 still
holds references to Unit3's structures (e.g., st_join_table). When
control returns to Unit2 for its own local cleanup, it accesses
already-freed memory.

Fix: move cleanup_stranded_units() to the end of cleanup(). This way,
each unit completes its own local cleanup first—clearing its
references to any child structures—before triggering cleanup of its
stranded (child) units. This enforces a parent-first cleanup order.
c6067cdf965a...
c6067cdf965a3c71abdca9bd73328b9fed38e1d2
Sergei Petrunia
MDEV-39368: Add --replay-server-manual.
bc70ec97eeb7...
bc70ec97eeb7594af4713c2a9818a8ffeaf384fe
PranavKTiwari
MDEV-39245: Validate plugin names are pure ASCII before registration

Previously, valid plugins were left in INACTIVE state in the internal
hash when a subsequent plugin in the same .so had a non-ASCII name.

Fixed by adding a pre-validation loop before registration that checks
all plugin names using my_string_repertoire(). If any name is non-ASCII,
the .so is rejected via plugin_dl_del() before any plugin is registered.
bba3146acf79...
bba3146acf79b2373179190857ca644547576ab6
Marko Mäkelä
MDEV-39263 innodb_snapshot_isolation fails to prevent lost updates under contention

lock_clust_rec_read_check_and_lock(): Refine the check whether
the transaction that last modified the record is still active.
The only thing that should matter is whether we are allowed to see
the record. If the implicit lock holder transaction was active and
we succeeded in acquiring the lock, this means that the transaction
had been committed. We must return DB_RECORD_CHANGED (ER_CHECKREAD)
in that case. We want to avoid returning it before the lock wait,
in case the other transaction will be rolled back.

Thanks to Vadim Tkachenko of Percona for reporting this bug,
as well as Kyle Kingsbury for the broader testing that led to this
finding. Vadim's test case was simplified by me and the root cause
analyzed with https://rr-project.org and an additional patch that
added std::this_thread::yield() at the start of
trx_t::commit_persist(). An even better spot should have been
right after the call to trx_t::commit_state().

The addition to the test innodb.lock_isolation is based on the work
by Teemu Ollakka, which was essential for refining this fix.

Reviewed by: Thirunarayanan Balathandayuthapani
9f659049da0d...
9f659049da0dbe1431f3e385763e14f86fa33720
Thirunarayanan Balathandayuthapani
MDEV-38842 Server fails to drop .ibd file when vector table creation fails

Problem:
========
When creating tables with vector indexes, if the secondary table
creation fails after the main table is successfully created,
the server was not properly cleaning up the main table's .ibd file.
Stale file exists because create_table_impl() always called
ddl_log_complete() on any error, which disables DDL log entries
instead of executing them for cleanup. The main table would be
left behind even though the overall CREATE TABLE operation failed.

Solution:
=========
Add ha_create_status enum to distinguish between different table
creation failure scenarios in ha_create_table():

- HA_CREATE_SUCCESS: Table created successfully
- HA_CREATE_FAILED_EARLY: Failure before storage engine file creation
- HA_CREATE_FAILED_SECONDARY: Failure during secondary table creation

This enum is being used in create_table_impl():

When HA_CREATE_FAILED_SECONDARY is returned, it indicates that the
main table files were successfully created but secondary table
creation failed. In this case, create_table_impl() calls
ddl_log_revert() to execute DDL log entries and clean up the
partially created main table files.

When HA_CREATE_FAILED_EARLY is returned, it indicates failure before
any files were created. In this case, create_table_impl() calls
ddl_log_complete() to disable the DDL log entries since there's
nothing to clean up.
97ece2bc81d9...
97ece2bc81d94d5166135c6b8515816b2702e6b2
Sergei Petrunia
MDEV-39368: Run set optimizer_replay_context='' for cleanup.
92b151bfbfbc...
92b151bfbfbc48266e13887aaaf014d381b125d9
Abhishek Bansal
MDEV-38474: ASAN heap-use-after-free in st_select_lex_unit::cleanup

cleanup_stranded_units() was added at the start of
st_select_lex_unit::cleanup() by 34a8209d6657. This causes a
use-after-free when nested subqueries are merged into their parent
unit. With nested subqueries like:

  SELECT * FROM t1
  WHERE a IN (SELECT b FROM t2
              WHERE a IN (SELECT c FROM t3 WHERE FALSE HAVING c < 0));

the stranded_clean_list chains the units as: Unit1 -> Unit2 -> Unit3.
Because cleanup_stranded_units() was called first, Unit1->cleanup()
would recursively trigger Unit2->cleanup(), which in turn would
trigger Unit3->cleanup(). Unit3's cleanup frees its heap-allocated
join structures. But since Unit3 was merged into Unit2, Unit2 still
holds references to Unit3's structures (e.g., st_join_table). When
control returns to Unit2 for its own local cleanup, it accesses
already-freed memory.

Fix: move cleanup_stranded_units() to the end of cleanup(). This way,
each unit completes its own local cleanup first—clearing its
references to any child structures—before triggering cleanup of its
stranded (child) units. This enforces a parent-first cleanup order.
8f814d3b626c...
8f814d3b626c1cdafa23df1ffb15ddcce6763c4b
PranavKTiwari
MDEV-39184- Rework MDL enum constants values.
Reverted enum_mdl_namespace code changes, as it doesn not add any value.
add vlaue.
8d0feb20729b...
8d0feb20729bdcb46667cf00515b0447b2cab077
Alexey Botchkov
MDEV-39210 ExtractValue/UpdateXML crash.

XML parser fixed to handle <! and <? correctly.
86a15de7c0fa...
86a15de7c0fa4fa07c7e4cfb141ed64e956694cd
Raghunandan Bhat
MDEV-39118: `test_if_hard_path` crashes on recursively resolving `$HOME`

Problem:
  When `$HOME` is set to `~/` (or any string starting with `~/`), the
  `home_dir` is initialized to that value. When `test_if_hard_path` is
  called on a path starting with `~/`, it replaces the `~/` prefix by
  recursively calling `test_if_hard_path(home_dir)` leading to infinite
  recursion and a crash.

Fix:
  Add a check in `test_if_hard_path` to see if `home_dir` itself begins
  with `~/`. If it does, skip the recursive call to prevent the
  infinite loop.
8039d7741613...
8039d77416132b0df65d44080dee9afe31f566e1
Aleksey Midenkov
MDEV-39184 TABLE_LIST C++-friendly initialization refactoring

The problem with the current initialization is that TABLE_LIST ctors
as well as init_one_table*() functions call reset() that byte-zeroes
the object after encapsulated objects were initialized by their
constructors. That specifically creates the wrong value for
mdl_request.type which must be MDL_NOT_INITIALIZED (-1) by default and
bzero() reverts it to MDL_INTENTION_EXCLUSIVE (0). And these constant
values is not easy (if not possible) to change.

The fix introduces utility base class Byte_zero which moves bzero()
call before the encapsulated ctors (as parent classes' ctors are
called first). So now encapsulated ctors are not called redundantly
and no double initialization is needed.

All the C++-constructed objects call init_one_table*() as before, only
without reset(). The C-alloced objects call init_one_tab*_r() versions
that call reset(). These will be replaced back to no-reset() versions
after their allocation is refactored to C++ version.
7ff88d8c30e6...
7ff88d8c30e6ddb4b483cc3233fe872790e5e28c
Sergei Petrunia
MDEV-39368: Make mtr write queries into log/replay_queries.log
7f8dc5004dad...
7f8dc5004dad6dcecc07d95e09714899b4f92f71
Dave Gosselin
MDEV-39209: use iterative cleanup for merged units to avoid stack overflow

Query optimization can merge derived tables (VIEWs being a type of derived
table) into outer queries, leaving behind stranded  st_select_lex_unit objects
("stranded units") for post-query cleanup.

Previously, these were cleaned up recursively. For queries with many merged
derived tables, the deep recursion over the list of stranded units could
exhaust the stack. This change replaces the recursive cleanup with an
iterative loop to prevent stack overflows.
6f2dad8604e9...
6f2dad8604e9db6e87063f21dc1650092ea1df38
Marko Mäkelä
Protect backup by log_sys.latch.wr_lock(), and make Windows happy
6c551cd65f4d...
6c551cd65f4dc28df124e6ce6869316080e2ca1b
Dave Gosselin
MDEV-39209: use iterative cleanup for merged units to avoid stack overflow

Query optimization can merge derived tables (VIEWs being a type of derived
table) into outer queries, leaving behind stranded  st_select_lex_unit objects
("stranded units") for post-query cleanup.

Previously, these were cleaned up recursively. For queries with many merged
derived tables, the deep recursion over the list of stranded units could
exhaust the stack. This change replaces the recursive cleanup with an
iterative loop to prevent stack overflows.
660d19206d2f...
660d19206d2f23f5a4ecd19f269162a0e2f165aa
PranavKTiwari
MDEV-39245- Check that plugin name is pure ASCII
Added plugin names in mariadb-test install under debian.
6562c87cbfac...
6562c87cbfac7681818b5f050b25880e1dee1fd2
Alexey Botchkov
MDEV-39124 XMLTYPE: allow only well-formed XML.

Necessary checks added to the XMLTYPE.
58f507206f0e...
58f507206f0ef93b582acd4551ee7668c6f966b5
Marko Mäkelä
Merge 10.6 into 10.11
562f69028ef1...
562f69028ef1371085f49a78bfb59cb67b3a3989
Marko Mäkelä
Protect backup by log_sys.latch.wr_lock(), and make Windows happy
4edfcf26fc59...
4edfcf26fc59929afe9f69836706d2eb1a9c0f07
Raghunandan Bhat
MDEV-39118: `test_if_hard_path` crashes on recursively resolving `$HOME`

Problem:
  When `$HOME` is set to `~/` (or any string starting with `~/`), the
  `home_dir` is initialized to that value. When `test_if_hard_path` is
  called on a path starting with `~/`, it replaces the `~/` prefix by
  recursively calling `test_if_hard_path(home_dir)` leading to infinite
  recursion and a crash.

Fix:
  Add a check in `test_if_hard_path` to see if `home_dir` itself begins
  with `~/`. If it does, skip the recursive call to prevent the
  infinite loop.
452df3fdfa28...
452df3fdfa28144578e6fc02cf54b5cc0dfce33b
Alexey Botchkov
MDEV-38767 XML datatype to be reported as format in extended metadata in protocol.

add respective Send_field metadata for UDT.
4299ea88cd45...
4299ea88cd450a44dd19df67215b940b5285fa3c
Marko Mäkelä
MDEV-39264: Improve the documentation of ER_CHECKREAD

Simlar to ER_LOCK_DEADLOCK and ER_LOCK_WAIT_TIMEOUT, let the ER_CHECKREAD
message suggest that the transaction needs to be restarted. When this error
is reported by InnoDB (only if innodb_snapshot_isolation=ON),
the transaction will be rolled back.
3c1d6b108c1f...
3c1d6b108c1fbe13cb0404a9a2106b5b67df5749
Marko Mäkelä
Fix GCC-16 -Wmaybe-uninitialized
372f1e00808d...
372f1e00808d100543e5992ec183b595d12a8d68
Alexey Botchkov
MDEV-39210 ExtractValue/UpdateXML crash.

test and a comment fixed.
316c3fbc4c3b...
316c3fbc4c3bb808f8127e137a47d5d56622c4af
Michael Widenius
MDEV-32745 Add a simple MySQL to MariaDB upgrade helper

The tool is named mariadb-migrate-config-file.
The main purpose of the tool is to change MySQL option
files to work both for MySQL and MariaDB.
There are options to do the changes in the options file inline,
or at-end-of-file. One can also remove or comment unknown options.

The list of supported options is generated compile time from
mariadbd --help. All server options, including compiled plugins, are
supported.

The bulk of the code comes from Väinö.
Monty has updated it with a lot of extra options.
Wlad helped with cmake integration

Other things:
- Fixed a memory leak in sql_plugin.cc
- plugin-load will now in case of errors try to load all given plugins
  before aborted
- If silent-startup is used, plugin-load will not give errors for
  plugins it cannot load or warnings about plugin marturity level.
- my_rm_tree() will now delete symlinks, not the actual file, if
  MY_NOSYMLINK flag is used.
- my_stat() will now give data for symlink if MY_NOSYMLINKS is used.
- Added 'number of lines' option to mysqltest --cat_file

@Authors: Väinö Mäkelä <[email protected]>,[email protected]
2a8d889b544b...
2a8d889b544bf76719c6ae4648b5e8efae211624
Aleksey Midenkov
MDEV-39184 Cleanup for MDL_NOT_INITIALIZED

As C++ style initialization of TABLE_LIST now works correctly after
Byte_zero refactoring. We may remove MDL_NOT_INITIALIZED double
initialiation.
12a9677e5b24...
12a9677e5b24e16196c1a1661ea931a7530c950b
Marko Mäkelä
MDEV-39264: Improve the documentation of ER_CHECKREAD

Similar to ER_LOCK_DEADLOCK and ER_LOCK_WAIT_TIMEOUT, let the ER_CHECKREAD
message suggest that the transaction needs to be restarted. When this error
is reported by InnoDB (only if innodb_snapshot_isolation=ON),
the transaction will be rolled back.
0d9db6bbcc55...
0d9db6bbcc5532e0bde0a63e5991cb5ebee060eb
Raghunandan Bhat
MDEV-37243: SP memory root protection disappears after a metadata change

Problem:
  When a stored routine involes a cursor and metadata of table on which
  the cursor is defined changes, the SP instruction has to be reparsed.
  For ex:
  CREATE OR REPLACE TABLE t1 (a INT);

  CREATE OR REPLACE FUNCTION f1() RETURNS INT
  BEGIN
    DECLARE vc INT DEFAULT 0;
    DECLARE cur CURSOR FOR SELECT a FROM t1;
    OPEN cur;
    FETCH cur INTO vc;
    CLOSE cur;
    RETURN vc;
  END;

  SELECT f1(); - first execution, sp-mem_root marked read-only on exec
  SELECT f1(); - read-only sp-mem_root
  ALTER TABLE t1 MODIFY a TEXT; - metadta change
  SELECT f1(); - reparse, rerun instr and mark new mem_root read-only

  sp_lex_instr is re-parsed after the metadata change, which sets up a
  new mem_root for reparsing. Once the instruction is re-parsed and
  re-executed(via reset_lex_and_exec_core), the new memory root assigned
  to the instruction being reparsed remains writable. This violates the
  invariant of SP memory root protection.

Fix:
  Mark the new memory root created for reparsing with read-only flag,
  after the first execution of the SP instruction.
05d98ff46192...
05d98ff4619229268c6571a86c426803f5782422
PranavKTiwari
MDEV-39245: Validate plugin names are pure ASCII before registration

Previously, valid plugins were left in INACTIVE state in the internal
hash when a subsequent plugin in the same .so had a non-ASCII name.

Fixed by adding a pre-validation loop before registration that checks
all plugin names using my_string_repertoire(). If any name is non-ASCII,
the .so is rejected via plugin_dl_del() before any plugin is registered.
0574e1babe89...
0574e1babe897d9bb3afc7ccd96d4476157c6e02
Alexey Botchkov
MDEV-39124 XMLTYPE: allow only well-formed XML.

Necessary checks added to the XMLTYPE.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Mon 20 Apr 2026 19:02:52 (UTC)