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
feb7dabf21f9...
feb7dabf21f951db09f38304be7b755936ee85bc
rusher
[misc] add maxscale testing
f860cb0f6489...
f860cb0f6489f02bd79b2431fad02d6409e04111
Monty
Added pcre2-8 for embedded server
ec45a0cbe48e...
ec45a0cbe48e204af016b7902613d6402fd47334
rusher
[misc] skip MaxScale-incompatible auth tests
e5f1ad3632df...
e5f1ad3632dfa5f30c45ec16bec570f71fecb3bd
Monty
MDEV-39095 MariaDB server syntax checker

Adds option --check-syntax to mariadbd server.

This allows one to check if mariadbd supports some particular syntax.

Example usage:
cat file-with-sql-syntax | mariadbd [--no-defaults] --check-syntax
e53fc93d0f65...
e53fc93d0f65a9b2916b36a76ffda9b41d1d420b
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Updated result files for some tests
de5efd064cca...
de5efd064ccadf0e886e5bc71f664072ae33fe0e
Michael Widenius
Remove wrongly included file columnstore...generated
d4ac1d6e140a...
d4ac1d6e140a8441b71f20dfbea51db483bcb00e
Monty
Fixed failing union test in main.group_by

This failed in buildbot on amd64-ubuntu-2204-debug-ps
c04226578033...
c0422657803395b12381e5208beb19515cd0a378
ParadoxV5
MDEV-38972 Refactor MDEV-37530 and MDEV-28302 to Use Internal Data Structures

We currently (should) use in-house data structures;
those in the C++ Standard Library are not yet formally approved.
Until that day comes (if ever),
this commit swaps the set of data structures.
As this commit contains no other significant refactoring,
this change from one library to the other is also
a sample for static and performance comparisons.
be5b9a72a0a4...
be5b9a72a0a472dbb9556ba55838c64516129d2a
rusher
[misc] add maxscale testing
bace8d948355...
bace8d948355e490078a8444bb3e18b2b64731a0
Dave Gosselin
MDEV-39397: Document and clean up dump_leaf_key

Add a docblock for dump_leaf_key that describes each parameter
and the leaf payload layout, and documents the return values and
side effects.

Sprinkle inline comments through the body to explain the LIMIT and
OFFSET bookkeeping, the dual purpose of result_finalized, why
borrowing table->record[1] as scratch space is safe, the offset
translation for skipped null bytes, and why the blob_storage
truncation flag is cleared after raising ER_CUT_VALUE_GROUP_CONCAT.

Implement other code cleanups, too, like dropping the unused tmp2
String object and rename old_length to starting_len so the cut_max_length
call reads more directly.  Other changes include narrowing loop
variables to the loop scope, move declarations next to their
first use, and replacing the C casts with static_cast.

There should be no behavior changes at this commit.
b1947f06a065...
b1947f06a0653b1660d4a94ccc379fd0bc065f85
rusher
[misc] maxscale CI test addition
aeb477b71a8b...
aeb477b71a8b5b7ddd3e01036f60f63aaebdcde4
Dave Gosselin
MDEV-23278: Incorrect Calculation with AVG() Function

Type_handler_int_result::Item_decimal_precision assumes that
max_length includes space for a sign, but Item_int literals don't
include such a space.  When aggregate_attributes_int propagates these
into functions via a Item_type_holder, the formula computes
precision-1 (or 0 for 1-digit cases), producing the incorrect
calculation with AVG.

This fix changes aggregate_attributes_int to follow the convention the
Type_handler expects, that max_length = max digit-count + (signed ? 1
: 0).  This matches the TODO comment that begins with "TODO: rewrite
aggregate_attributes_int()... " which suggested this idea.
a5eb56703467...
a5eb56703467f082d7a15c83fe4d14ec66284381
Marko Mäkelä
squash! 8bf07427966559ba36e94d35e8bd41941d219dfd

log_t::checkpoint_age_max(): Return the maximum checkpoint age.

log_t::archive_new_write(): If the log file would overflow,
increase innodb_log_file_size to the next multiple of 4096 bytes.

log_write_up_to(): Remove a redundant buf_flush_ahead() call.
The call will be triggered in mini-transaction commit based
on the return value of log_close().
a5be717559a5...
a5be717559a502206a717135020ca7f0b52f5625
rusher
[misc] add maxscale testing
  • cc-alma8-aarch64: build linux-connector_c failed -  stdio
  • cc-alma9-aarch64: build linux-connector_c failed -  stdio
  • cc-alma9-amd64: build linux-connector_c failed -  stdio
  • cc-bookworm-aarch64: build linux-connector_c failed -  stdio
  • cc-bookworm-amd64: build linux-connector_c failed -  stdio
  • cc-bullseye-aarch64: build linux-connector_c failed -  stdio
  • cc-bullseye-amd64: build linux-connector_c failed -  stdio
  • cc-buster-aarch64: build linux-connector_c failed -  stdio
  • cc-buster-amd64: build linux-connector_c failed -  stdio
  • cc-fedora37-amd64: build linux-connector_c failed -  stdio
  • cc-fedora38-amd64: build linux-connector_c failed -  stdio
  • cc-fedora39-amd64: build linux-connector_c failed -  stdio
  • cc-focal-aarch64: build linux-connector_c failed -  stdio
  • cc-focal-amd64: build linux-connector_c failed -  stdio
  • cc-jammy-aarch64: build linux-connector_c failed -  stdio
  • cc-jammy-amd64: build linux-connector_c failed -  stdio
  • cc-noble-aarch64: build linux-connector_c failed -  stdio
  • cc-noble-amd64: build linux-connector_c failed -  stdio
  • cc-rhel8-aarch64: build linux-connector_c failed -  stdio
  • cc-rhel8-amd64: build linux-connector_c failed -  stdio
  • cc-rhel9-aarch64: build linux-connector_c failed -  stdio
  • cc-rhel9-amd64: build linux-connector_c failed -  stdio
  • cc-rocky8-aarch64: build linux-connector_c failed -  stdio
  • cc-sles15-amd64: build linux-connector_c failed -  stdio
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
a4f0981a0f45...
a4f0981a0f45c657e290d26994767003c4bdf3a5
Dave Gosselin
MDEV-23278: Incorrect Calculation with AVG() Function

Type_handler_int_result::Item_decimal_precision assumes that
max_length includes space for a sign, but Item_int literals don't
include such a space.  When aggregate_attributes_int propagates these
into functions via a Item_type_holder, the formula computes
precision-1 (or 0 for 1-digit cases), producing the incorrect
calculation with AVG.

This fix changes aggregate_attributes_int to follow the convention the
Type_handler expects, that max_length = max digit-count + (signed ? 1
: 0).  This matches the TODO comment that begins with "TODO: rewrite
aggregate_attributes_int()... " which suggested this idea.
93bb9266666a...
93bb9266666a0a838187679ad2cc14af169895da
rusher
[misc] Skip test_conc26 on MaxScale
900b503704b2...
900b503704b28b46562b19394ef6f33d618f9818
rusher
[misc] maxscale CI test addition
8ddc0f8971a8...
8ddc0f8971a8c0d3987eb931ee2fc64895e8e463
rusher
[misc] add maxscale testing
8d9820144fc1...
8d9820144fc142fe7adf8f8d74770f3d177868f8
Monty
Added pcre2-8 for embedded server
8541f6369611...
8541f63696113e2a2e0400bad3acc7e26e991a02
rusher
[misc] maxscale CI test addition
7ef884ba3b9d...
7ef884ba3b9d603f274b802cae7de7bc3e8ffa4f
rusher
[misc] add maxscale testing
7828fb475b00...
7828fb475b00d4211ba8ce1ec6e9a1b06e0fc39b
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]
7475e41b4ed0...
7475e41b4ed0a01e60009bbbdfa3ee26f31ce73d
ParadoxV5
MDEV-39482: Remove `@@relay_log_info_file` MySQL/MariaDB 5.5 format test

MariaDB 5.5 has been EOL for 6 years, and MySQL 5.5 for almost 7½ years.
Code improvements are therefore no longer obliged to retain a
slightly divergent path that supports upgrades from those versions.
72ac648d8cca...
72ac648d8ccad6a75e4474df74cb08803c0279b9
Monty
MDEV-39095 MariaDB server syntax checker

Adds option --check-syntax to mariadbd server.

This allows one to check if mariadbd supports some particular syntax.

Example usage:
cat file-with-sql-syntax | mariadbd [--no-defaults] --check-syntax
72261abd1d14...
72261abd1d14aea1bec12180e52a7008248bb829
rusher
[misc] maxscale CI test addition
6ea4ce73e004...
6ea4ce73e004f1cfc6b3897a6b8004bea6df43cc
Dave Gosselin
MDEV-39397: GROUP_CONCAT of BIT returns decimal, not packed bytes

When DISTINCT or ORDER BY is in play, GROUP_CONCAT builds an
internal temp table and converts BIT arguments to integers so records
can be compared by memcmp.  Calling val_str() on that field
then returned the decimal form ("0", "1", "3") instead of the
packed bit bytes that Field_bit::val_str() emits everywhere else,
including the "plain" GROUP_CONCAT path.

Override get_str_from_field() for Item_func_group_concat to detect
when the argument is BIT, read the value as an integer from the
temp table field, and pack it into (max_length + 7) / 8 bytes,
mirroring Field_bit::val_str().  This makes DISTINCT and ORDER BY
agree with the plain path.

Before this change, BIT fields in group_concat were rendered
as ASCII which was incorrect and produced the wrong result as
described in the ticket.  With this fix, we also update the
existing test cases to wrap BIT columns with '+0' so the recorded
output stays in ASCII format.  Now, with this patch and the test
case from the ticket, MariaDB and MySQL produce identical resultset
of a single row, single column having value 08.

By default, a group_concat including BIT fields on MySQL returns a
hexified value for its resultset whereas MariaDB requires the
hex() function to wrap group_concat for the same result:

Setup:
  create table t1(a bit(2), b varchar(10), c bit);
  insert into t1 values (1, 'a', 0), (0, 'b', 1);

MySQL:
  mysql> select group_concat(a, c) from t1;
  +----------------------------------------+
  | group_concat(a, c)                    |
  +----------------------------------------+
  | 0x01002C0001                          |
  +----------------------------------------+
  1 row in set (0.001 sec)

MariaDB:
  MariaDB [test]> select hex(group_concat(a, c)) from t1;
  +-------------------------+
  | hex(group_concat(a, c)) |
  +-------------------------+
  | 01002C0001              |
  +-------------------------+
  1 row in set (0.001 sec)
5e541901ec84...
5e541901ec84e5e3dbc602b7eca26013ea11113f
Michael Widenius
Remove some compiler warnings from mroonga
5133eace029a...
5133eace029ae8e246ee428c7fa56c7cca94e6f8
Monty
Fix compilation eror because of -Wframe-larger-than= in sql_show.cc

gcc 15.1.15 gives the following error, possible from static struct
initialization:

/my/maria-11.8/sql/sql_show.cc: In function ‘void __static_initialization_and_destruction_0()’:
/my/maria-11.8/sql/sql_show.cc:11356:1: error: the frame size of 62880 bytes is larger than 16384 bytes [-Werror=frame-larger-than=]

Fixed by adding PRAGMA_DISABLE_CHECK_STACK_FRAME to sql_show.cc
494943e6a3ca...
494943e6a3ca58f1625c7953f471b46f37061a06
rusher
[misc] maxscale CI test addition
3f20c98e9d27...
3f20c98e9d2768034b6fa287fa080b211c080a89
rusher
Fix handling of length_value for fixed-size temporal types after libmariadb CONC-812 change

libmariadb CONC-812 changed mysql_stmt_bind_result to initialize length_value=0 for fixed-size struct types (DATE/TIME/DATETIME/TIMESTAMP). While the MYSQL_TIME buffer is still correctly filled by ps_fetch_datetime, length_value is no longer set to sizeof(MYSQL_TIME). Use buffer_length as fallback when length_value is 0 for temporal types.
3b0abd9b18c0...
3b0abd9b18c04c13f0e11779afc7b365470d9aa1
rusher
[misc] maxscale CI test addition
3618d807034c...
3618d807034cf6b9ed4531711c2ace07bcebe03a
Marko Mäkelä
squash! e3e4c0ba16eb57674a640e0e7f5e950afef6b3c9

log_t::checkpoint_age_max(): Return the maximum checkpoint age.

log_t::archive_new_write(): If the log file would overflow,
increase innodb_log_file_size to the next multiple of 4096 bytes.

log_write_up_to(): Remove a redundant buf_flush_ahead() call.
The call will be triggered in mini-transaction commit based
on the return value of log_close().
2c4c2ff9cdf9...
2c4c2ff9cdf9b9deaf017a4df80389fe6b0eb60b
rusher
[misc] maxscale CI test addition
2850387fd547...
2850387fd54734d0fe83e3592370a62f09fec0c7
rusher
[misc] maxscale CI test addition
1e575c00db5a...
1e575c00db5aeeab01ed9c56bc6f4afdbbbe5ff2
rusher
[misc] add maxscale testing
1a84b31dd7e2...
1a84b31dd7e27e2e2f7f04375d47089f9f725d13
ParadoxV5
Move `Info_file`s’ `VALUE_LIST`s to for-each

This commit refactors the static lists of bulky member pointer
substitutes to instance-level lists of on-demand references.

The choice of these static lists was an aggressive optimization.
Once operations reduce dependence on saving and loading, e.g., for crash
safety in non-GTID mode, that improvement will no longer be significant.
16633ac421f4...
16633ac421f42bae58078c5c17987b75405f221c
Monty
Have mariadbd server read [mariadb-X] and [mariadb-X] sections

X is major version, like mariadb-11 and mariadbd-11

This simplifies my.cnf files supporting many MariaDB versions
06906fcb1dbb...
06906fcb1dbb27a2a3f4560c8eb0e5e72d96df11
rusher
[misc] add maxscale testing
00657aca7058...
00657aca7058889144c1a92d69c6b8502d79174b
rusher
[misc] Skip test_conc26 on MaxScale

(cherry picked from commit 93bb9266666a0a838187679ad2cc14af169895da)
  • cc-alma8-aarch64: build linux-connector_c failed -  stdio
  • cc-alma9-aarch64: build linux-connector_c failed -  stdio
  • cc-alma9-amd64: build linux-connector_c failed -  stdio
  • cc-bookworm-aarch64: build linux-connector_c failed -  stdio
  • cc-bookworm-amd64: build linux-connector_c failed -  stdio
  • cc-bullseye-aarch64: build linux-connector_c failed -  stdio
  • cc-bullseye-amd64: build linux-connector_c failed -  stdio
  • cc-buster-aarch64: build linux-connector_c failed -  stdio
  • cc-buster-amd64: build linux-connector_c failed -  stdio
  • cc-fedora37-amd64: build linux-connector_c failed -  stdio
  • cc-fedora38-amd64: build linux-connector_c failed -  stdio
  • cc-fedora39-amd64: build linux-connector_c failed -  stdio
  • cc-focal-aarch64: build linux-connector_c failed -  stdio
  • cc-focal-amd64: build linux-connector_c failed -  stdio
  • cc-jammy-aarch64: build linux-connector_c failed -  stdio
  • cc-jammy-amd64: build linux-connector_c failed -  stdio
  • cc-noble-aarch64: build linux-connector_c failed -  stdio
  • cc-noble-amd64: build linux-connector_c failed -  stdio
  • cc-rhel8-aarch64: build linux-connector_c failed -  stdio
  • cc-rhel8-amd64: build linux-connector_c failed -  stdio
  • cc-rhel9-aarch64: build linux-connector_c failed -  stdio
  • cc-rhel9-amd64: build linux-connector_c failed -  stdio
  • cc-rocky8-aarch64: build linux-connector_c failed -  stdio
  • cc-sles15-amd64: build linux-connector_c failed -  stdio
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
BuildBot (0.8.9) working for the MariaDB project.
Page built: Fri 01 May 2026 23:57:36 (UTC)