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
f79685d16b69...
f79685d16b69f102f33d9265b719c7600ae494a7
Alessandro Vetere
fixup! fixup! MDEV-37070  Implement table options to enable/disable features
eb3bb9bdb43b...
eb3bb9bdb43b3e0a9415c1cf19583bfb4afac83c
Sergei Petrunia
Fixup to previous commit
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
dc4ea8b58b0e...
dc4ea8b58b0e11372acdb0add65f2d7b479251e6
Sergei Petrunia
Add unit test for json_read_object.
cfffdc8687a9...
cfffdc8687a926e1e7ec77b95159830193421507
Sergei Petrunia
Cleanup: remove read-side structures that have write-side copies

Remove:
-class range_context_for_replay;
-class irc_context_for_replay;
-class rir_context_for_replay;
cb7e864c20c2...
cb7e864c20c21fe1e23d263ce26844086e1b893a
Mohammad Tafzeel Shams
MDEV-22186: Add innodb_trim_core_file to exclude InnoDB memory from cores

Problem:
There is no control to include or exclude large InnoDB memory regions
such as the buffer pool and log buffer from core files, which can lead to
unnecessarily large core dumps or prevent capturing useful memory state.

Solution:
Introduce a new global dynamic system variable innodb_trim_core_file that
allows excluding large InnoDB memory regions (buffer pool and log buffer)
from core dumps using MADV_DONTDUMP where supported. When enabled and
@@core_file=ON, the server marks relevant memory regions to be omitted
from core files. The madvise state is dynamically updated when the
variable changes.

Additionally, a test helper script is introduced to inspect
/proc/<pid>/smaps and verify whether large memory regions are marked
for trimming.

- innodb_trim_core_file
  Global boolean system variable controlling whether InnoDB memory
  regions should be excluded from core dumps. Has no effect if
  @@core_file=OFF. Default: ON on non-debug builds with MADV_DONTDUMP
  support, OFF otherwise.

- innobase_should_trim_core_dump()
  Determines whether InnoDB memory allocations should be marked with
  MADV_DONTDUMP, based on @@core_file and @@innodb_trim_core_file.

- innodb_srv_trim_core_file_update()
  Update hook that sets srv_trim_core_file and triggers runtime updates
  of madvise state for both the buffer pool and log buffers.

- srv_trim_core_file
  Global variable backing @@innodb_trim_core_file.

- buf_pool_t::buf_pool_should_madvise_dont_dump
  Tracks the current madvise state for the buffer pool memory.

- buf_pool_t::madvise_update_dump()
  Re-evaluates whether the buffer pool should be excluded from core
  dumps and applies ut_dontdump() or ut_dodump() accordingly.

- buf_pool_t::create()
  Initializes madvise state based on innobase_should_trim_core_dump()
  and conditionally applies MADV_DONTDUMP to the buffer pool memory.

- buf_pool_t::resize()
  Reapplies MADV_DONTDUMP to newly allocated memory regions when
  resizing if innodb_trim_core_file=ON

- log_t::log_buf_should_madvise_dont_dump
  Tracks the madvise state for the InnoDB log buffers.

- log_t::madvise_dontdump()
  Marks log buffers and resize buffers with MADV_DONTDUMP.

- log_t::madvise_dodump()
  Restores inclusion of log buffers in core dumps using MADV_DODUMP.

- log_t::madvise_update_dump()
  Updates the madvise state for log buffers when
  @@innodb_trim_core_file changes.

- log_t::attach()
  Call ut_dodump() for log_t::buf & log_t::flush_buf on successful
  allocation and innodb_trim_core_file=OFF

- log_t::resize_start()
  Call ut_dodump() for log_t::resize_buf & log_t::resize_flush_buf on
  successful allocation and innodb_trim_core_file=OFF

- check_core_dump_trim.inc
  Test helper that inspects /proc/<pid>/smaps to detect memory regions
  with the dd VmFlag and determine whether the core file is expected
  to be trimmed based on buffer pool and log buffer sizes.
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.
c1e2731ceb65...
c1e2731ceb65f9309b6f76882163e86f71f20360
Dmitry Shulga
Fixed the test events.events_restart
c01cb01bcfb5...
c01cb01bcfb5667ff8393b35e962f0a01b83bf7c
Sergei Petrunia
Small cleanups. Remove table_context_for_replay::ddl
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.
a3c2a17d3648...
a3c2a17d3648447300170c0ebe9d2c4742cfca22
forkfun
MDEV-38967: STR_TO_DATE() cannot be used in indexed virtual columns

Update STR_TO_DATE() to accept an optional third argument for the locale.
DATE_FORMAT() and STR_TO_DATE() return NULL when the locale argument is NULL;
issue a warning and fall back to the session @@lc_time_names for invalid locale names.
STR_TO_DATE() can now be used in indexed virtual columns while having all 3 arguments,
but not allowed when 2 as it depends then on the session @@lc_time_names
a33b205660a6...
a33b205660a687e589d91b433f9c476bae0e868a
ParadoxV5
MDEV-38907 Optimistic Relay Log Crash Recovery

This commit adds an automatic recovery
procedure to GTID relay log initialization.

This procedure scans the write end of a log to remove any
trailing (or corrupted) incomplete event or event group.
Unlike `@@relay_log_recovery`, this procedure won’t discard
the portion of logs that managed to survive the crash.
For exceptional cases that require manual intervention,
`@@relay_log_recovery` is not altered.

Note, because START SLAVE purges the relay log in GTID mode,
this feature doesn’t bring immediate value.
However, this commit is a crash-safety
preparation for lifting that limitation.
Non-GTID mode can also build upon this procedure
to improve its crash safety precautions.

Reviewed-by: Kristian Nielsen <[email protected]>
78c3db0628a1...
78c3db0628a1420159e147f6883860a48b3e0e8f
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Follow-up to fix issue with starting server on server with broken table mysql.event
757e3edc62c0...
757e3edc62c0ae7246a160b9366aef04ff09c8bf
Dmitry Shulga
Fixed the test events.events_restart
71abe072935d...
71abe072935d94fb2c1156b6256d84a3d62e6534
Marko Mäkelä
fixup! 1d57f26b50436d3e59ccce9a2b8cd7a9836c07ac

buf_flush_sync_for_checkpoint(): Prevent a shutdown hang
when innodb_log_recovery_target is set.
6e938a68f267...
6e938a68f267858889d78e7c6aa827053cd16bde
Sergei Petrunia
Coding style renames: Saved_index_stats, Saved_table_stats
6e5911fe9471...
6e5911fe94718a357c952d0072021ee3376a07c0
Sergei Petrunia
Improve comments and readability.
6a53cebe0273...
6a53cebe02735cfd44466f18d96b986b8cf4b825
Sergei Petrunia
Fix for sub-statements: handle PROCEDURE also.
628a91720c00...
628a91720c00aa4128ca9f57a105910a7025b024
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.
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.
618662ec58b9...
618662ec58b950b70b3d63ebbb89e6fdfa09a549
Sergei Petrunia
JSON parsing: rename classes to cleaner names

Read_container_value -> Read_array.
Read_list_of_context -> Read_array_into_list
5db12570137d...
5db12570137dd1a60821b92f34a9e84b1e990024
Alexey Botchkov
MDEV-37262 XMLTYPE: validation.
  13.03
54e61c0defbc...
54e61c0defbca9e2df962951674011677b88ddfc
Marko Mäkelä
fixup! 32b7005d3463f95a03bf1dd9e7be4b59f3f9f591
4f12d3c36302...
4f12d3c36302baf2416054dc743d3273225e1d04
Alessandro Vetere
fixup! MDEV-37070  Implement table options to enable/disable features
4bea18af44e1...
4bea18af44e15dc0b6218a210432e3e42450408c
bsrikanth-mariadb
MDEV-38803: Rename 2 files

change opt_store_replay_context.h and .cc files to
opt_context_store_replay.h and .cc respectively
4bdd5f928b68...
4bdd5f928b68f657d696e20e0d74866b0d6bf38d
Alexey Botchkov
MDEV-37262 XMLTYPE: validation.
3d3b52282838...
3d3b52282838b55707077c822cc1057977a92077
ParadoxV5
[to squash] a coupa fixes for ci

Some issues might be existing bugs, where relay log open
errors leads to further problems similar to MDEV-24625.
3cb524f8619c...
3cb524f8619c0279957af502956781e688904c4c
Sergei Petrunia
Further code cleanups. Don't print empty objects for VIEWs.
37a2cff9345d...
37a2cff9345d0e54e7c80374bd016ad148e75e90
Sergei Petrunia
Fixup (2)
3766b0d1ca85...
3766b0d1ca8555b2963ee9863c88179aae89382c
luckyxhq
MDEV-38915 Fix signed/unsigned type mismatch in setval() for GET_ULONG
33cd18545b21...
33cd18545b2173dc450e375015ce6745c7d73b1d
forkfun
MDEV-38967: STR_TO_DATE() cannot be used in indexed virtual columns

Update STR_TO_DATE() to accept an optional third argument for the locale.
DATE_FORMAT() and STR_TO_DATE() return NULL when the locale argument is NULL;
issue a warning and fall back to the session @@lc_time_names for invalid locale names.
STR_TO_DATE() can now be used in indexed virtual columns while having all 3 arguments,
but not allowed when 2 as it depends then on the session @@lc_time_names
2bfad4613974...
2bfad46139744b14c1d2f05dee710b36a81ab7d3
bsrikanth-mariadb
MDEV-38805: use charset utf8mb4, for client-server communication

REPLACE INTO statements would now use my_charset_utf8mb4_bin conversion
Also, the sql_script file structure would now look like

SET NAMES utf8mb4;
SET var1=value1;
.
.
CREATE DATABASE 'name' if NOT..;
USE DATABASE 'name';
CREATE TABLE ...;
.
REPLACE INTO ..;
.
.
set @opt_context='...';
.
.

Additionally, made few changes to the documentation comments
1eb671e2f2bc...
1eb671e2f2bc33ecb0f3180ee9cff76ee2e98e4f
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.
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.
1b7c2bd8e28d...
1b7c2bd8e28dc26786a9a7937c5cb4b1138f65af
Marko Mäkelä
fixup! 1d57f26b50436d3e59ccce9a2b8cd7a9836c07ac

Allow the last checkpoint slot to be overwritten after recovery
0f8cb60b56fe...
0f8cb60b56fe19f71d3628739d06ee523f585afd
Sergei Petrunia
Rename dump_XXXX() functions and make them more readable.
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.
065b166d6e5b...
065b166d6e5b176dd8a6a113a8e88c3f1d02dec4
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.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Sat 14 Mar 2026 15:45:39 (UTC)