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
ed0b3c99dc5d...
ed0b3c99dc5d5b96aa303c23c630ad295aa00fdc
Lawrin Novitsky
Increased min required smake version to 3.10

To eliminate the cmake warning and to trigger the build
e938a0d6a64d...
e938a0d6a64db1699c08ef50ae649617c0952729
Georg Richter
Fix CONC-626: don't revalidate certificate after COM_CHANGE_USER

Before client sends COM_CHANGE_USER the client needs to clear
tls_verification_status to avoid server certificate verification.
e796d0ac04b2...
e796d0ac04b217ecb2e8045f1c62aeb30feacf49
PranavKTiwari
MDEV-36990: SIGFPE in get_max_range_rowid_filter_elems_for_table
Reject key definitions where a column contributes zero bytes to an index
but is part of a PRIMARY KEY (or otherwise semantically NOT NULL) and no
hash-based index fallback is used.

Previously, ALTER TABLE allowing BINARY(0) as part of a PRIMARY KEY could
produce a zero-length clustered index. This propagated into InnoDB as
tab->file->ref_length == 0, leading to division-by-zero in
get_max_range_rowid_filter_elems_for_table() during optimizer cost
estimation.

This change enforces validation in init_key_part_spec() to ensure that
PRIMARY KEY columns cannot have effective key length 0, preventing invalid
index creation and downstream optimizer/runtime crashes.
e76be95dd135...
e76be95dd135a9ed8244e52dddc3c045f55218c0
Lawrin Novitsky
Made prepearedstatement testsuite not to force CSPS for defautl connection

This way it can be controlled via params/env which typ of PS is tested.
Tests requiring CSPS should take care of that
d9c364ec4dc9...
d9c364ec4dc967ffa7a02a030c5b2c1fa8faf8a7
Jan Lindström
MDEV-38870 : Galera test failure on galera.MDEV-38201

Test changes only. Moved wait condition where node should
disconnect from cluster because it has become inconsistent.
After that next FLUSH HOST based on timing could return
not supported or timeout.
d81857f68790...
d81857f68790459df13ac22f4e5467d4dafe5136
Vladislav Vaintroub
MDEV-40115 DENY EXECUTE hides unrelated routines in SHOW commands or I_S

Fix check_routine_level_acl() to pass parent access, for accurate
calculation.

Previously, if (db_level_access & privs) returned 0, it was treated as
no-access on DB level in check_some_routine_access().

This is not the complete truth, with DENY, it may mean there is access,
but some routines have DENY. So pass the db level grants/denies to the
function for more accurate checking.
d7eb10106c1a...
d7eb10106c1af99e645fb0eb5c7eee3eed136cbc
Lawrin Novitsky
CONCPP-157, CONCPP-158 setBytes() parameter is sent as binary type in

binary protocol. It is sent as MYSQL_TYPE_BLOB. As counterpart, binary
types received from the server via binary protocol are now converted
to int types - berfore the exception would be thrown right away w/out
any attempt to convert.
d0dd89fb47c9...
d0dd89fb47c962ccc05dfe6fc509645edb74230c
pranavktiwari
Merge branch '10.11' into 10.11-MDEV-30297
cbaa0fc1df69...
cbaa0fc1df69b971987ce9abfcca9b5c250ec813
Pekka Lampio
MDEV-38386 Fix incomplete cleanup in Galera MTR tests failing under --repeat

A number of Galera MTR tests pass on the first run but fail on a second
--repeat iteration, because server, cluster or filesystem state leaks
across runs and the test does not restore a clean starting state.

Fix the cleanup (or force a fresh cluster) in the affected tests. Each
fix was verified with --repeat=2 --force.

1. Stale async-slave GTID position (11 tests)

  RESET SLAVE [ALL] does not clear gtid_slave_pos. As the master does
  RESET MASTER in cleanup, on the next run the slave considers the
  events already applied and skips them, so the replicated tables never
  appear. Clear the position with SET GLOBAL gtid_slave_pos = "".

2. Leftover binlog GTID state from trailing cleanup (1 test)

  Trailing DROP TABLE / mtr.add_suppression statements ran after the
  .inc's reset master and re-populated node_2's binlog. gtid_binlog_state
  keeps the latest seqno per (domain, server_id) pair, so a stray
  0-2-<n> survived into the next run and broke the state comparison.
  Reorder the cleanup and reset node_2's binlog last.

3. Cluster-global, one-time or time-window state (11 tests)

  The wsrep GTID domain seqno is cluster-global and is not reset by
  reset master (nor by a mid-test SST rejoin); error-log contents,
  warning-flood suppression timers and one-time bootstrap behaviour are
  likewise not restored by in-test cleanup. Force a fresh cluster with
  include/force_restart.inc.

4. Leftover filesystem artifacts (1 test)

  mariabackup refuses to back up into a non-empty target directory, so
  the leftover target dirs from the previous run made the backup fail
  silently and the expected log messages never appeared. Remove the
  target directories in cleanup.
caafc23878e0...
caafc23878e010f11d602777e4e2ed812118fd57
Dave Gosselin
MDEV-39207:  mark test as not_embedded

Test fails on embedded CI because original not_embedded flag was not preserved
c88a12e5ace3...
c88a12e5ace3391387ee4c5f4c1a33df4e0aff6e
Thirunarayanan Balathandayuthapani
MDEV-39706  Assertion `!thd || !coordinator_thd' failed

Problem:
========
  - This assert was introduced in commit
0152c617e80ccf3f33d3ea4b50c17d5f588613b1 (MDEV-39261), which sets
coordinator_thd in clone_oldest_view() and resets it to nullptr in
batch_cleanup() at the end of the batch.
When innodb_trx_purge_view_update_only_debug is enabled, InnoDB fail
to reset coordinator_thd. As a result, InnoDB fails with assert in
next batch

Solution:
========
trx_purge(): Reset coordinator_thd to nullptr when
innodb_trx_purge_view_update_only_debug is enabled.
c79ca44f24ad...
c79ca44f24ad5cd8bb45a06e8ad91a73e4148c55
Daniel Black
MDEV-31209 Queries with window functions do not obey KILL / max_statement_time

Window functions run in a loop in
Frame_cursor::compute_values_for_current_row which can include a large
number of rows.

Adjust this function to check for the current thd being killed by only
every 256 rows, so as not to destroy any CPU pipelining or similar.
b45a3a41a2d5...
b45a3a41a2d580ec54c8c5396a9eb6bdb681babe
PranavKTiwari
Added test case.
b1627d4317cb...
b1627d4317cb1575c209bd8ebc1efa89beea3b4b
Lawrin Novitsky
CONCPP-153 Parameter value escaping did not consider the charset

In case of client side statement prepare, if the data is encoded in multibyte
charsets, escaping of string and binary parameter could lead to incorrect data
that in its turn could let sql injection with charsets like big5, gbk, sjis, cp932.

The fix considers the charset now. The testcase has been added.
ae136494fb2a...
ae136494fb2a447d74c0e6cc747461f96e2ec17f
Fariha Shaikh
MDEV-39928 Fix GitLab CI centos9 job failure

The centos9 job uses yum-builddep -y mariadb-server to install build
dependencies, but the mariadb-server source package has been removed
from CentOS Stream 9 repositories. Replace with explicit installation of
the required build dependencies.

All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
a7a2bfda2a15...
a7a2bfda2a15b8b42693f3d99d8b27edb023fe31
Dave Gosselin
MDEV-39952:  Skip tests that need mariabackup

Skips tests that require mariabackup if mariabackup was not
built (WITH_MARIABACKUP=OFF).

Backport of the same MTR change from 12.3 but applied to
additional tests.
a5e70cc7e7d1...
a5e70cc7e7d115a8b6ecaf03933dbba6b9462270
Yuchen Pei
MDEV-40048 [to-squash] Allow trigger and LOCK TABLES to work with range interval auto partitioning

When a range interval auto partitioned table is the target of a
trigger, the triggering statement is not necessarily one that would
cause the auto-creation of new partitions, so we need to account for
that.

Also added support for LOCK TABLES ... WRITE.

Improved tests coverage by adapting tests from versioning.partition.
96ca4d3d5aa4...
96ca4d3d5aa416eb26c4de8bf3e681bb5185ae5e
Dave Gosselin
MDEV-38158:  Incorrect query result

When setup_copy_fields() needs to copy a non-aggregate function value,
it doesn't construct an Item_copy directly.  Instead, it calls
Type_handler::create_item_copy, which is a kind of factory.  The base
Type_handler::create_item_copy returns Item_copy_string.  Some type
handlers override it, like timestamp and fixed binary.  However, the
numeric type handlers (e.g., float, double, int, decimal) did not, so
they fell through to that base and got Item_copy_string.

A SELECT that aggregates will copy each non aggregate function value
into a temporary table through an Item_copy object, whose concrete
type is chosen by the create_item_copy method on the value's type
handler.  For numeric types that method returned Item_copy_string,
which stores the value as text.  A FLOAT keeps only FLT_DIG
significant digits as text, too few to reproduce its 24 bit mantissa,
so the copied value differed from the original.  With one row per
group, CAST(c1 AS FLOAT) - MIN(CAST(c1 AS FLOAT)) returned a large
number instead of zero.

Add Item_copy_real with Item_copy_float and Item_copy_double variants
that keep the value as a double, the same way Item_cache_real does, and
let the float and double type handlers create them.  This mirrors the
existing copy items for timestamp and fixed binary types.
947931d1c412...
947931d1c4129eb497598a2c4097e96b4c797f00
Fariha Shaikh
MDEV-39931 Fix main.socket_conflict failure when running as root

The test directly executes $MYSQLD via --exec, bypassing MTR's automatic
--user=root injection. In GitLab CI containers where tests run as root,
mariadbd refuses to start and the test fails.

Skip the test when running as root, matching the existing approach used
by the related main.bad_startup_options test.

All new code of the whole pull request, including one or several files
that are either new files or modified ones, are contributed under the
BSD-new license. I am contributing on behalf of my employer Amazon Web
Services, Inc.
8c4283b7859e...
8c4283b7859ed20600f5016aa0215c9feb49e9a7
Vladislav Vaintroub
MDEV-40115 DENY EXECUTE hides unrelated routines in SHOW commands or I_S

Fix check_routine_level_acl() to pass parent access, for accurate
calculation.

Previously, if (db_level_access & privs) returned 0, it was treated as
no-access on DB level in check_some_routine_access().

This is not the complete truth, with DENY, it may mean there is access,
but some routines have DENY. So pass the db level grants/denies to the
function for more accurate checking.
8581099fb85f...
8581099fb85f90d61df7fb8e822f528d709d39ca
Lawrin Novitsky
Minor formatting changes
821fe49dbbb2...
821fe49dbbb29235f721ebdfbefad17002f0272c
Vladislav Vaintroub
MDEV-40001 my_sync() does not use NtFlushBuffersFileEx()

Copy the logic from Innodb. Use a fallback to FlushFileBuffers(), if
NtFlushBuffersFileEx() fails.

my_winfile.c is renamed to my_winfile.cc, since it is using a C++ feature,
initialization of global variable using non-constant expression.
Exported functions remain extern "C"
820b1f96d1d4...
820b1f96d1d487bc74cb91aeb24be6fcadab1156
PranavKTiwari
Added logic for colum typ.
741ece2da49a...
741ece2da49a7de49ff4cba8d3943a362f1d42b5
Kristian Nielsen
MDEV-40057: Virtual column included in after-image with unique BLOB index, asserts

Do not put any virtual column values into the before-image or after-image of
row events.

These virtual column values were causing assertion and probably other issues
as well. Concretely, a UNIQUE index on (int_col, blob_col) where the int_col
is being updated would include the hidden virtual column for the index in
the after-image, without including the value of the blob_col in
binlog_row_image=MINIMAL. This would cause an assertion during
TABLE::update_virtual_fields() due to missing bit in the bitmap.

Even if it doesn't cause an assertion, including the virtual column values
makes no sense, as they are recomputed anyway on the slave when applying the
row events.

Also fix excessive allocations of memory for table object bitmaps.

Signed-off-by: Kristian Nielsen <[email protected]>
659834a6fc8e...
659834a6fc8ea3248140e3b95be0b6bcdb4fae25
Alexey Botchkov
MDEV-36261 XMLTYPE: methods - step 1

Method functions added to the XMLTYPE.
64d385ced998...
64d385ced99885bd289b8854027aca9328f53ce2
Lawrin Novitsky
CONCPP-152 fix of effect of C/C resetting length of fixed size types

The driver was using that length directly. Now it tests the length and
use either it or buffer length.
6277bb34ad89...
6277bb34ad89c69fab300b03aa4103ef6ee103d2
Thirunarayanan Balathandayuthapani
MDEV-39707 Assertion `lsn != 0' failed in log_write_up_to

Problem:
========
innodb_make_page_dirty(): Unconditionally calls log_write_up_to()
with mtr.commit_lsn() after committing the mini-transaction.
When the mtr produced no redo records when the targeted page
is full of zeroes.

Solution:
========
innodb_make_page_dirty(): Skip log_write_up_to() when
commit_lsn() is zero.
40d62288111b...
40d62288111b511f7002561947869aa732e25f54
Kristian Nielsen
Fix inconsistent terminology

Signed-off-by: Kristian Nielsen <[email protected]>
3c684f1e6942...
3c684f1e694281a48c257496f09ccc61dde960fc
Oleg Smirnov
MDEV-36344: UBSAN Lifo_buffer::have_space_for change

Adjust Lifo_buffer::have_space_for to not lead itself to UBSAN
overflows.
3113e0ea2a6f...
3113e0ea2a6fa2c9d187f07b86a358d150052c56
Kristian Nielsen
MDEV-40057: Virtual column included in after-image with unique BLOB index, asserts

Do not put any virtual column values into the before-image or after-image of
row events.

These virtual column values were causing assertion and probably other issues
as well. Concretely, a UNIQUE index on (int_col, blob_col) where the int_col
is being updated would include the hidden virtual column for the index in
the after-image, without including the value of the blob_col in
binlog_row_image=MINIMAL. This would cause an assertion during
TABLE::update_virtual_fields() due to missing bit in the bitmap.

Even if it doesn't cause an assertion, including the virtual column values
makes no sense, as they are recomputed anyway on the slave when applying the
row events.

Also fix excessive allocations of memory for table object bitmaps.

Signed-off-by: Kristian Nielsen <[email protected]>
29e43967f4f2...
29e43967f4f2c1a1d4af3372354bd203b8418152
Sergei Golubchik
only check for duckdb stuff if target duckdb is enabled
28bb3959482a...
28bb3959482a1c3c23f36ce131a12e1f69e52edc
PranavKTiwari
MDEV-36990: SIGFPE in get_max_range_rowid_filter_elems_for_table
Reject key definitions where a column contributes zero bytes to an index
but is part of a PRIMARY KEY (or otherwise semantically NOT NULL) and no
hash-based index fallback is used.

Previously, ALTER TABLE allowing BINARY(0) as part of a PRIMARY KEY could
produce a zero-length clustered index. This propagated into InnoDB as
tab->file->ref_length == 0, leading to division-by-zero in
get_max_range_rowid_filter_elems_for_table() during optimizer cost
estimation.

This change enforces validation in init_key_part_spec() to ensure that
PRIMARY KEY columns cannot have effective key length 0, preventing invalid
index creation and downstream optimizer/runtime crashes.
1fb075512a7a...
1fb075512a7aeab8646a163cbb6f265c49f4c075
Sergei Golubchik
refactor submodule.cmake to fetch less

don't update all submodules automatically,
only update those that are actually used by the build
1bd4b8bccc14...
1bd4b8bccc149ce1331e56534e4293179300f210
Yuchen Pei
MDEV-40088 [to-squash] Disallow subqueries in INTERVAL clause in range interval auto partitioning

This is consistent with system time (versioning) partitioning. Also
consistent is that both allow expressions otherwise.
1538c75d6141...
1538c75d61410ef5ce9e94d16a4b99482e505c48
Thirunarayanan Balathandayuthapani
MDEV-39706  Assertion `!thd || !coordinator_thd' failed

Problem:
========
  - This assert was introduced in commit
0152c617e80ccf3f33d3ea4b50c17d5f588613b1 (MDEV-39261), which sets
coordinator_thd in clone_oldest_view() and resets it to nullptr in
batch_cleanup() at the end of the batch.
When innodb_trx_purge_view_update_only_debug is enabled, InnoDB fail
to reset coordinator_thd. As a result, InnoDB fails with assert in
next batch

Solution:
========
trx_purge(): Reset coordinator_thd to nullptr when
innodb_trx_purge_view_update_only_debug is enabled.
0cb2cc959eb4...
0cb2cc959eb4ecaed42deadb5eb93e13dd6835e3
Dmitry Shulga
MDEV-40004: Server crashes in sp_head::register_instr_mem_root_for_deallocation upon shutdown

n shutdown server could crash in case triggers executed during server run
and some of triggers instructions were re-compiled.

The crash is caused by attempt to allocate a memory for storing pointers
on mem_roots used for memory allocation taken place on re-parsing failing
trigger's statements. The reason of crash is dereferencing of nullptr
returning by the function current_thd().

To fix the issue, use dummy THD on shutdown the table definition cache.
tdc_start_shutdown() is solely invoked from the function clean_up()
but the later is called from many places around the source code, not only
from mysql_main(), particularly clean_up() is called from unireg_abort().
Therefore, the extra argument added into the signature of the function
cleanup() to allow explicit request of use dummy THD on shutdown the table
definition cache.
0aad50a0390b...
0aad50a0390ba44a9f8c4182b7a8c71a1a104309
PranavKTiwari
MDEV-36990: SIGFPE in get_max_range_rowid_filter_elems_for_table

Reject zero-length key parts for columns that are effectively non-nullable
in key context.

Previously, key validation relied solely on NOT_NULL_FLAG to reject
zero-length key parts. During ALTER TABLE processing, PRIMARY KEY columns
may not yet have their implicit NOT NULL property reflected in
Create_field::flags, allowing definitions such as BINARY(0) in a PRIMARY
KEY to bypass validation.

This could produce a zero-length clustered index and propagate
tab->file->ref_length == 0 into the optimizer, leading to a
division-by-zero in get_max_range_rowid_filter_elems_for_table().

Strengthen validation in init_key_part_spec() by rejecting zero-length key
parts for columns that are explicitly NOT NULL or belong to a PRIMARY KEY,
even when NOT_NULL_FLAG has not yet been materialized during ALTER TABLE
processing.
087a948e2e46...
087a948e2e4620901d2c358b46907a15b0987059
Daniel Black
MDEV-36344: UBSAN DsMrr_impl::dsmrr_init on null ptr

Under SQL_SELECT::test_quick_select there isn't
a mrr buffer. The TRP_RANGE.mrr_buf_size is explictly
sets its size to 0 in get_best_index_intersect.

Rather than hit undefined behaviour in what
eventually results in full_buf being nullptr,
jump the case and go directly to use_default_impl.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Fri 19 Jun 2026 19:20:44 (UTC)