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
fc9d1564cf72...
fc9d1564cf72bc291abd1d55849a77e2d3046733
Rucha Deodhar
MDEV-39119: Improve error handling when using OLD_VALUE as alias name

Analysis:
Since OLD_VALUE_SYM was part of reserved keywords, it did not allow
old_value in the alias.
Fix:
Change OLD_VALUE_SYM from reserved keyword to keyword_sp_var_and_label.
f62764ebbcb6...
f62764ebbcb650d3a6b29fb5260279b7e39c2360
Rex Johnston
MDEV-38070 wrong resultset with having and or condition

During join execution of a query involving an aggregation,
ref items pointing to types that call Item_ref::val_native
(which includes TIMESTAMP fields) will return a value from
Item_field::field, rather than Item_field::result_field.
This will result in a potentially incorrect grouping comparison
and an incorrect result.

Affected statements will involve a derived grouped table with
an aggregation function TIMESTAMP field and outer having clause.
ed78f526006f...
ed78f526006fa3a86863c0ea16f27bfa39cd6657
mohitbalwani
MDEV-38696 Fix infinite loop in my_copy() function

The bug occurred when my_read() returned (size_t)-1 but was
compared against (uint)-1.It was causing the loop to
never exit when reading from a directory or other error conditions.

Changed comparison from (uint)-1 to (size_t)-1 to match the
return type of my_read().
ebc94391cfd4...
ebc94391cfd4e8f3e5bb41894c0a3c66557cddde
Marko Mäkelä
MDEV-39087 os_file_set_size() may behave inconsistently during shutdown

os_file_set_size(): Ignore srv_shutdown_state and consistently extend
the file to completion. If someone is in a hurry, they can forcibly
kill the mariadbd process and test the crash recovery.
ebae058ae3d6...
ebae058ae3d63d8633db48dd6231d37a7f552b4c
Hemant Dangi
MDEV-36621: galera.GCF-360 test: IST failure

Removed redundant per-node wsrep_provider_options overrides that
were dropping all timeout settings.
e78756fe20fe...
e78756fe20fecf3dc69bcfa629518e44a0a9698c
Marko Mäkelä
MDEV-39139 InnoDB fails to start up with small RLIMIT_AS

innodb_init_params(): When no innodb_buffer_pool_size_max has been
specified, cap the default to a quarter of the address space limit.

Reviewed by: Vladislav Vaintroub
e6b8cacfb99e...
e6b8cacfb99ec4da1e759147987150afcfb3644b
Marko Mäkelä
Merge 11.4 into 11.8
dee748aebdb6...
dee748aebdb658fb6b15e9c1a38289bf3d81e579
Abdelrahman Hedia
MDEV-37842 Skip implicit Using_Gtid warning when value is unchanged

When a replica already has Using_Gtid=No and a CHANGE MASTER TO is
issued with log coordinates (e.g. relay_log_pos, master_log_file),
the server emits a spurious warning:

  Note 4190 CHANGE MASTER TO is implicitly changing the value of
  'Using_Gtid' from 'No' to 'No'

The value isn't actually changing, so the warning is misleading.

In change_master() (sql/sql_repl.cc), when log coordinates are specified
without an explicit master_use_gtid, the code implicitly sets Using_Gtid
to No and emits a warning. The condition only checks whether
master_use_gtid=No was explicitly given but does not check whether
Using_Gtid is already No.

Added a check that the current Using_Gtid value differs from
USE_GTID_NO before emitting the warning. The warning now only fires
when the value actually changes.

Re-recorded rpl.rpl_from_mysql80 which previously expected the
spurious No-to-No warning.

Reviewed-by: Georgi Kodinov <[email protected]>
Reviewed-by: Brandon Nesterenko <[email protected]>

https://github.com/MariaDB/server/pull/4678
d116cace9b9c...
d116cace9b9c12814482d0274cb19f6f50fde60f
Vladislav Vaintroub
Revert "MDEV-38989 main.ctype_utf16le SEGV in Ubuntu 26.04 (x86-64-v3)"

This reverts commit 6318d5001597fff28ea7ba7f957d66edd7e3e954.

uint2korr is now fixed in MDEV-37788, thus partial workarounds are not necessary anymore.
c45a0d8678c9...
c45a0d8678c963033678afd1dd962259033c2b4d
Geng Tian
MDEV-38454 CHANGE MASTER TO master_heartbeat_period does not accept numbers with `+` sign

Fixed parser inconsistency where CHANGE MASTER TO master_heartbeat_period
rejected numeric values with an explicit '+' sign, while other parameters
like master_connect_retry accepted them.

The issue was in sql/sql_yacc.yy where master_heartbeat_period used
NUM_literal (which doesn't accept '+'), while other parameters used
ulong_num (which includes opt_plus).

Solution: Added opt_plus before NUM_literal in the master_heartbeat_period
grammar rule, making it consistent with other numeric parameters.

Added test case to verify:
- master_heartbeat_period=+60 now works (was broken)
- master_heartbeat_period=60 still works (backward compatible)

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.
b9153f5ab565...
b9153f5ab56599f3d258ee28e4b8e0f96f08c215
Vladislav Vaintroub
MDEV-39027 suboptimal code for InnoDB big endian access functions

Optimize big endian (and some little endian) Innodb access functions by
using my_htobeN/my_betohN and memcpy.
b69cb60a83d1...
b69cb60a83d1da736f8594ecc11583430d3aac34
Christian Hesse
systemd: add missing quotes in examples

The line is commented, but let's have valid quoting anyway...
b07a36ee3295...
b07a36ee329569b9b2a4b373a1b16fe2dc3ed32a
Marko Mäkelä
Merge 10.11 into 11.4
af0057aa045f...
af0057aa045faa8103e57308228f6bc83e8477f9
Daniel Black
MDEV-39086 MSAN/UBSAN/ASAN builds run without basic optimization

MSAN/UBSAN/ASAN/TSAN builds are preforming addition runtime
checks requiring additional CPU to do so. To help the test
systems of these run with a bit faster, but still be debuggable,
we should add -Og where another C/CXX optimization flag isn't
specified.

Gcc/Clang environment that support these range of sanitizers
use -O followed by 0-3, g, s, z, and apparently "fast". These
are the flags matched by the regex.
ad5ef77e1882...
ad5ef77e18825135836cc7774b04b4c43f7446b6
Varun Deep Saini
MDEV-33070 Thread pool starvation at oversubscribe

Allow one more worker at the oversubscribe threshold so a group
only becomes oversubscribed after it exceeds the configured
limit.

Add a regression test that reproduces the starvation case in the
generic thread pool and verifies queued work still drains.

Signed-off-by: Varun Deep Saini <[email protected]>
9f8f6d24dbf2...
9f8f6d24dbf23c7293a1fd437f1605eeeb0d42df
Denis Protivensky
MDEV-39011: Fix THD leak in async slave error path with wsrep_restart_slave

- fix the leak by properly releasing resources before repeat
- rework the error path handling to wait for Wsrep readiness state
  instead of repeating endlessly
- improve Wsrep readiness state by also singlaing node's shutdown
920b2c656b33...
920b2c656b33f4aa05e63829c708f707360e75d4
Aleksey Midenkov
MDEV-38798 Assertion `mdl_key->length() == 3' failed in MDL_map::find_or_insert

MDEV-33985 wrongly checked db.length for pure alias, but
empty_c_string is not pure alias. Reverted this check to db.str.
8ac04937fb1d...
8ac04937fb1deb61a9634d8218f1048145630853
Vladislav Vaintroub
MDEV-37788 fix uintNkorr/intNstore macros to avoid unaligned access

Replaced macros with optimized inline functions, that use memcpy
instead of unaligned access (translates to single instruction
on architectures we support). Used compiler byteswap intrinsics
where appropriate.

Removed byte_order_generic.h as well as Intel specific headers
byte_order_generic_{x86|x86_64}.h

Added some casts to places where intNstore writes into "const char*".
88d34d5c8339...
88d34d5c8339beb02e15c93155f78b84050f5aa1
Yuchen Pei
MDEV-38732 Correctly construct queries with NULL uservar values in spider

The subsequent assertion failure in end_statement is likely caused by
HA_ERR_OUT_OF_MEM not correctly handled, but it should not return an
HA_ERR_OUT_OF_MEM here in the first place.
807bfd05d8e4...
807bfd05d8e499aab1bed04ecbc8ccc3df542e23
Marko Mäkelä
MDEV-39040 log_sys.latch performance lost to PERFORMANCE_SCHEMA

log_sys.latch: Remove the PERFORMANCE_SCHEMA instrumentation.
We already know that this is a very busy latch. All code paths
where a shared log_sys.latch is being held should already be
highly optimized. The few paths where an exclusive log_sys.latch
is being held are known to be potentially problematic, but rare.

Removing the PERFORMANCE_SCHEMA instrumentation for this latch
is expected to improve performance. On a quick Sysbench run with

performance_schema_instrument=wait/synch/rwlock/%=on

I observed an 2.9% improvement on throughput.

srw_lock_debug_simple: A non-instrumented version of srw_lock_debug,
to allow PERFORMANCE_SCHEMA to work WITH_INNODB_EXTRA_DEBUG=ON.

Reviewed by: Alessandro Vetere
7f8121f2d835...
7f8121f2d8353dceeae2487e0631fad53911aa22
Marko Mäkelä
Make innodb_log_recovery_start settable (for incremental backup)

Also, implement a little more of backup_innodb.
7c037714fe52...
7c037714fe528548c88c885a4f21c35daf4b6ae1
Sutou Kouhei
MDEV-39098: UBSAN: insufficient-object-size in mroonga groonga/lib/db.c:10882

The incorrect destructor was used in delete_reference_records_in_index
75c868b3007d...
75c868b3007d1321fdbe6d08cba67a6582d15d83
Anway Durge
MDEV-XXXXX: Fix Mroonga post-install script path

Update legacy /usr/share/mysql path to /usr/share/mariadb in the debian postinst script for the mroonga plugin.
656070a2cde1...
656070a2cde1652cc35911221e71e1dc3aed6330
Fariha Shaikh
MDEV-38020 Master & relay log info files read 2^31 and above incorrectly

Master and relay log positions are 64-bit unsigned but were read using
atoi(), which only handles signed 32-bit integers. Values >= 2^31 overflow
and corrupt after restart.

Add init_ullongvar_from_file() using my_strtoll10() to correctly parse
64-bit values. Update rpl_rli.cc and rpl_mi.cc to use ulonglong variables
and this new function.

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.

Reviewed-by: Brandon Nesterenko <[email protected]>
652d3d2c08ee...
652d3d2c08ee90563cb2d77736987f5d849ba91c
Daniel Black
MDEV-39109 main.sp-error stack overflow debug, MSAN and ASAN

MSAN seems error on stack depth 39 so set limit to 20.

ASAN error-ed on stack depth 248 so set limit to 200.

The actua;ly depth wasn't important for the purposes
of the fatal error handling in MySQL bug #15192
from which this test originates.

Reviewed/Approved by: Oleksandr "Sanja" Byelkin ([email protected])
6198f3f93d04...
6198f3f93d04e222f89e9a1caeacf0705c9ce6d1
Fariha Shaikh
MDEV-36725 Fix innodb_ctype_ldml test in view-protocol mode

The test innodb.innodb_ctype_ldml was failing in view-protocol mode due
to different column naming behavior for complex expressions.

Without explicit column aliases, view-protocol mode generates automatic
names (Name_exp_1, Name_exp_2) while normal mode uses the full
expression as the column name.

Add explicit column aliases to SELECT statements in innodb_ctype_ldml to
ensure consistent column names across both normal and view-protocol
modes.

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.
5fe4d03f2604...
5fe4d03f26045d1215e894d16054935ddd65ecc0
Georg Richter
Fix for CONC-812:

The `length` element of the MYSQL_BIND structure is
used to obtain the size of variable-length data
types, such as BLOBs or strings, in order to
determine the required buffer size, as described in
the documentation:

"Pointer to the length of the buffer (not used for
parameters). The length is ignored for numeric and
fixed-size data types, as the buffer_type value
determines the size of the data."

Since the prepared statement implementation of
MariaDB Connector/C is based on the PHP mysqlnd
extension code, the initial implementation
incorrectly set the `length` field for fixed-size
data types.

As agreed with the support team, we do not remove
the `length` value for fixed-size types, but retain
it to handle NULL values correctly.
52e9f3e7aa94...
52e9f3e7aa94721b24cf62471397ec8e936b8dfe
Mohamed
MDEV-38494 .mariadb_history rename race condition

When multiple mariadb sessions exit at the same time, they all write
to the same $HISTFILE.TMP then rename it to $HISTFILE.  The second
rename fails with Errcode 2 because the first already moved the file.

Fix: include the process PID in the temp file name so each session
uses its own unique path and no rename collision can occur.
3fe04b1e1882...
3fe04b1e1882e11e2a43bed8be0bc841d5d6dc8b
Marko Mäkelä
Merge 10.11 into 11.4
3c32991a4122...
3c32991a4122a2b67fbfa20375a11f70a00cc802
Daniel Black
Bump columnstore to latest stable-23.10
3ab87db19b82...
3ab87db19b823e64d991c1b1705cc58f69ffa46e
Marko Mäkelä
MDEV-39104 Hang in the test innodb.log_file_size,debug

srv_prepare_to_delete_redo_log_file(), srv_start(): When injecting a
failure, resume the ability to write a checkpoint, so that the
shutdown will not hang. Also, adjust the test so that it tolerates
the checkpoint during shutdown.

Fixes up commit bf363a573ab8f96657545de97ead568d09a9f1a0 (MDEV-38968)
3766b0d1ca85...
3766b0d1ca8555b2963ee9863c88179aae89382c
luckyxhq
MDEV-38915 Fix signed/unsigned type mismatch in setval() for GET_ULONG
2d2ec64fb439...
2d2ec64fb439d703d74f44a22795a0a56a9474ce
Aleksey Midenkov
MDEV-38854 Assertion table->vers_write fails upon ODKU into table with versioned column

In MDEV-25644 vers_check_update() sets vers_write to false in case it
returns false. It is ok for UPDATE but is not correct for ODKU is bulk
insert requires vers_write on next tuple.

The fix return vers_write value back when vers_check_update() and
related vers_insert_history_row() are done in ODKU.
1e639cb76d79...
1e639cb76d7999186e95a8cf1f69607742933051
Marko Mäkelä
Merge 10.6 into 10.11
1e3b820f2cdd...
1e3b820f2cdd77616680bbc5422d32c554cb9cdb
Denis Protivensky
MDEV-30612: Fix usage of lex->definer in wsrep_create_trigger_query

Setting thd->lex->definer is excessive as it's only used within the
function call.
Moreover, it would lead to a use-after-free on the second execution
of a CREATE TRIGGER prepared statement.
1abec9a9f8f6...
1abec9a9f8f660abf3a6d6177a49f4c2fe628fa8
Brian White
fix build with WITH_EXTRA_CHARSETS=none again
1357e575c03e...
1357e575c03e8d280976131f2d7dd8f310227c48
Jan Lindström
MDEV-38895 : Regression on MDL conflict handling

The reason for this timeout is a regression introduced in commit
https://github.com/MariaDB/server/commit/e40277d29b7c531e1ed6b3bed7ecfc8cfeff4c7e.
Where there is incorrect condition wsrep_thd_is_BF(granted_thd, false)
because if granted thread is BF it may not be BF-killed.

In this patch following has been changed
    * Split wsrep_handle_mdl_conflict to smaller easier to understand parts
    * Improved code comments
    * Improved debug logging to contain thread ids and necessary information
    * Corrected and simplified conditions so that BF threads are not killed
    * Added few debug assertions to verify that BF threads are not killed
    * Code cleanups so that tab-characters are not used
    * Existing test cases already test rest of the cases
0d3440e68286...
0d3440e682865f3d450dfb2c0151f539ad9bc60b
hadeer
Mroonga: fix SIGSEGV on NULL mroonga_log_file

Add mrn_log_file_check() to validate that
mroonga_log_file is not set to NULL or an empty
string, which previously caused a segfault.
0a93b393d04b...
0a93b393d04b5b3111d5e13cb171a64c1822beee
Alexey Yurchenko
MDEV-38383 Fix MDEV-38073 MTR test warning

MDEV-38073 MTR test started to fail with a warning after upstream merge
from 11.4 a7528a6190807281d3224e4e67a9b76083a202a6 because THD responsible
for creating SST user became read-only when the server was started with
--transaction-read-only=TRUE.
make sure the readonly flag on THDs created for wsp::thd utility class is
cleared regardless of the --transaction-read-only value as it is intended
only for client-facing THDs.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Mon 23 Mar 2026 13:04:00 (UTC)