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
fa9e10d02e9f...
fa9e10d02e9fa2be1ba041c1558ff83319f42ce0
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Core implementation

- Extended the sql grammar to support creation of system triggers
  on startup/shutdown
- System triggers metadata is loaded from the table mysql.event
- Events and system triggers share the same name space since both
  stored in the table mysql.event declared with the PRIMARY KEY (`db`,`name`)
  In result, attempt to create an event with the same name as existent
  trigger and vice versa results in failure with the new error
  ER_TRG_EVENT_CONFLICTS_NAME
- System triggers can be created only by users with the SUPER privilege
- Added the option --sys_triggers for mysqldump to dump system triggers.
  The option is turned off by default.
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
d4ac1d6e140a...
d4ac1d6e140a8441b71f20dfbea51db483bcb00e
Monty
Fixed failing union test in main.group_by

This failed in buildbot on amd64-ubuntu-2204-debug-ps
d1632c811fe2...
d1632c811fe242973c079551709ec6269406dfdb
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Extended the system table mysql.event to support creation of
system triggers (startup, shutdown, logon, logoff) and ddl triggers.

The system table mysql.event is extended with three columns
  `kind`, `when`, `ddl_type`.
For the task MDEV-30645 only the column `kind` is required,
the other two columns are required for the tasks
  MENT-2355, MENT-2291
but since it is better to reduce a number of times the system table
is changed and as a consequences a number of upgrades to be run,
the entire set of columns is added at once.

Type of the columns `kind` and `ddl_type` are specified as SET to allow
storing of triggers that handle several events.
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
bc73afe105bc...
bc73afe105bc41052cbc1fbd3ce96ae078c5774a
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Follow-up to fix the issue with starting server on a data dictionary
with broken table mysql.event or on its previous version without
columns required for storing metadata about triggers.
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
afea4555e76a...
afea4555e76a8ef5f706a04923f59fb41dcc8fc5
PranavKTiwari
MDEV-38839: Fix assertion in close_thread_tables on CREATE TABLE...SELECT FOR UPDATE with MyISAM temp table in MIXED binlog mode

FOR UPDATE on a MyISAM temp table acquires TL_WRITE due to lack of
row-level locking, causing STMT_WRITES_TEMP_NON_TRANS_TABLE to be set
incorrectly for a read-only access in CREATE TABLE...SELECT FOR UPDATE.
This blocked binlog_truncate_trx_cache() in MIXED mode leaving row
events stranded in the cache and triggering the assertion.

Fix: In the binlog table access flag loop, set
STMT_READS_TEMP_NON_TRANS_TABLE instead of
STMT_WRITES_TEMP_NON_TRANS_TABLE for source temp tables in
CREATE TABLE...SELECT. Add stmt_writes_to_non_trans_temp_table() and
use it in MYSQL_BIN_LOG::write() instead of
stmt_accessed_non_trans_temp_table() to ensure
mark_modified_non_trans_temp_table() is called only for genuine writes.
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.
a5f211ac378b...
a5f211ac378ba9bf38f97e48d76750e33993d961
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Follow-up to fix building with EMBEDDED server. Since support of
events isn't compiled in for embedded server but some stuff from
implementation of events is used for support of triggers, common
source code used both for events and triggers was extracted into
the separate files event_common.cc/event_common.h
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
7efbb0d0b267...
7efbb0d0b267a9548d58574179bac056a173931f
Daniel Black
MDEV-38913: pam_mariadb_mtr.so installation path change

This reverts the effect of MDEV-21654 and includes
pam_mariadb_mtr in the mariadb-test-data Deb package.

This allows our CI systems to run tests on the
pam implementation on Debian systems.

As the pam configuration can include a full path,
we've change the installation of the pam module
pam_mariadb_mtr.so to under the /usr/lib*/plugins/test_pam_modules
directory and configured the pam configuration file,
suite/plugins/pam/mariadb_mtr, to include the
full path to pam_mariadb_mtr.so.
7ef884ba3b9d...
7ef884ba3b9d603f274b802cae7de7bc3e8ffa4f
rusher
[misc] add maxscale testing
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
723ecde02bff...
723ecde02bffb9b71b03f3bdcbe953dd57d05c82
Daniel Black
MDEV-38979 RocksDB TLS destructor called after dlclose

During the mariadb application exit, the TLS desctructors
where called, but the function was previously dlclosed
so it wasn't available.

On the assumption that this is STB_GNU_UNIQUE, we disable
this optimization with -fno-gnu-unique.
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)
5ca4ab639ad5...
5ca4ab639ad5f99d74f794b54ba1b4d6182ec2a9
Georg Richter
MDEV-39509: Fix "invalid iv length" with OpenSSL 4.0

OpenSSL 4.0 changed the behavior of EVP_CIPHER_CTX_new:
It now initializes the internal iv_len with a sentinel
value of -1. When calling EVP_CipherInit_ex with the
cipher, key, and IV simultaneously, the provider validates
the IV against this sentinel before the cipher's default
metadata is applied, triggering an error.

This patch implements a two-stage initialization for OpenSSL 4.0+:
- Call EVP_CipherInit_ex with only the cipher to "thaw" the
  context and set the correct default iv_len.
- Perform a second call to provide the actual Key and IV data.

This approach ensures compatibility with OpenSSL 4.0 while
avoiding EVP_CipherInit_ex2 to maintain support for FIPS mode
and older versions.
58ff35c597b1...
58ff35c597b195698c9ace9ee3e5862113748c68
PranavKTiwari
MDEV-38839 Assertion (thd->state_flags & Open_tables_state::BACKUPS_AVAIL) || !thd->has_pending_row_events() failed in close_thread_tables on CREATE TABLE
In MYSQL_BIN_LOG::write(), mark_modified_non_trans_temp_table() was called on any access to a non-trans temp table. FOR UPDATE on a MyISAM temp table acquires TL_WRITE due to lack of row-level locking, causing the flag to be set incorrectly for a read-only access. This blocked binlog_truncate_trx_cache() in MIXED mode leaving row events stranded in the cache and triggering the assertion.
Fix: restrict mark_modified_non_trans_temp_table() to only when actual row modification events (WRITE/UPDATE/DELETE) are being written, using the existing LOG_EVENT_IS_WRITE_ROW(), LOG_EVENT_IS_UPDATE_ROW() and LOG_EVENT_IS_DELETE_ROW() helpers.
"
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
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.
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: Sun 03 May 2026 13:51:30 (UTC)