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
fa27a4a732e3...
fa27a4a732e3b56f24dad122f16e7e074068d159
Oleksandr Byelkin
new columnstore
f51edd8933e3...
f51edd8933e3b7c9e796864c7e6c61e25828b4b4
Fariha Shaikh
MDEV-39153 Fix sporadic main.change_master_default mismatch

The test used "restart_abort:" in the expect file, which MTR never
recognized. It fell through to the else branch, deleted restart_opts,
and started the server with defaults (heartbeat_period=60 instead of 0).

Replace restart_abort with direct --exec $MYSQLD calls.

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.
ed733d22fa63...
ed733d22fa63edb71dc23a7b9f24e3183261fed3
bsrikanth-mariadb
MDEV-39226: Push whole multi-table update/delete down into engines

Give storage engines a way to take over an entire multi-table
UPDATE/DELETE, the way they can already take over a SELECT. Without it the
join, the row matching and every modification run in the SQL layer even
when an engine could do the whole statement itself in one step; a
single-table UPDATE/DELETE already avoids this via
direct_update_rows()/direct_delete_rows(), but a multi-table statement has
no primary handler object to drive that path.

This adds a generic, engine-agnostic pushdown interface: the SQL layer
offers the statement to the engine, and if the engine accepts it, it
performs the whole thing and reports only the row counts.

- Split select_handler into a pushdown_handler base with select_handler
  (result set) and a new multi_upddel_handler (runs a whole UPDATE/DELETE,
  reports row counts, reported as PUSHED UPDATE/PUSHED DELETE); add
  handlerton::create_multi_upddel, looked up in Sql_cmd_dml::execute_inner().
- multi_update/multi_delete gain direct_update_delete_done(), which records
  the engine's counts so send_eof() binlogs and replies without the
  SQL-layer loop; it forces statement-format binlogging so the change still
  replicates under binlog_format=ROW, and errors out instead of silently
  dropping counts for an unsupported result object.
- FederatedX implements the interface as the reference engine used to test
  correctness: it prints the statement back and runs it remotely, passes
  the engine's error code/SQLSTATE through, reads the matched count from the
  remote info string, executes IGNORE locally, and only pushes down when all
  tables share one remote server (same as SELECT/derived/unit pushdown).

Test: federated.federatedx_pushdown_upd_del.
e3076650a9d6...
e3076650a9d600e2bee165b2aedd60ccf917d8e7
PranavKTiwari
MDEV-38633: Row events in statement based binlog: optimization possible?
A failing multi-table UPDATE or DELETE marked every target temporary table as not up to date in the binary log, even when nothing had been changed.
Any later statement reading such a table was then forced to use row logging.
Only mark the tables when something was actually changed—that is, when rows were updated/deleted or a non-transactional table was modified.
If nothing changed, set THD::tmp_table_binlog_handled so that mark_tmp_table_as_free_for_reuse() does not mark them either.
e23eb0b8a9e0...
e23eb0b8a9e04e31c7be7d5bdd17569211da653e
Oleksandr Byelkin
Merge fix
de031d056032...
de031d056032c9c27db73aa471e4a79ae92c56eb
Marko Mäkelä
squash! e16b1b4e2739be7bc8e91643b0a71e1f04a1b02f

BACKUP SERVER TO observes secure_file_priv
d646e24f7f7b...
d646e24f7f7b24dec695d8ebc5471f9b939dff8a
Alexander Barkov
MDEV-40009 SIGSEGV in Sql_path::from_text

Problem:
- The string passed to Sql_path::from_text() could be in
  various character sets, returned by Item::val_str_ascii(),
  which is not necessarily utf8mb3.
- While the code in Sql_path::from_text() was written in the way
  that "str" was considered to be in utf8mb3.
- As as result, cs->charset() in this line:
    auto len = cs->charlen(curr, end);
  could return a negative value and the whole loop got stuck.

Changes:
- Fixing Sys_var_path::from_item() to use val_str() instead of val_str_ascii(),
  to get the original value from "item", without any conversion.
- Moving the conversion code inside Sql_path::from_text().
c62d7895c35c...
c62d7895c35cafe00a0d516778ddfbd2ab66028e
Daniel Black
sql_test: mallinfo2 msan exclusion no longer needed

MSAN interceptor was added in clang-18.1.
c567deb95ad7...
c567deb95ad7469875b2e2f442bad4f492588db7
Oleksandr Byelkin
Merge branch '11.4' into bb-11.4-release
c4c860ec549c...
c4c860ec549cb65d7d112121ff8524507e8fc353
Oleksandr Byelkin
Merge branch '11.8' into bb-11.8-release
bc3939b84b71...
bc3939b84b71baa816cf9011fd04f7bbbf43dffd
Daniel Black
MDEV-17846 Wrong result with grouping select (fix)

Prevent unused variable 'ref_type'  warnings on non-debug builds.
bb0ac437015d...
bb0ac437015dec04fbee226745a8eb2bb4825917
Yuchen Pei
MDEV-40486 Length check for vector fields in CREATE TABLE ... SELECT

The changes of MDEV-39558 2b6529426a7e7c65d286e093d84138be9dcc34a3
added length check assertion in Field_varstring constructors, and
length check in type inference for SELECT set operations, to emit
errors before reaching the assertions.

That change caused an error to turn into an assertion failure in a
separate path, when the length limit violation is not detected before
tripping the assertion. So in this patch we fix it by adding an
earlier length check in that path.

The reason that we place this check inside
Item_func_vec_fromtext::fix_length_and_dec rather than say
`create_field_for_create_select is for consistency:

If

create table t1 as select
vec_fromtext(concat('[',group_concat(1),']')) as c1 from seq_1_to_64;

fails due to length limit violation, then so should

create table t1 (v vector(64) not null);
insert into t1 select vec_fromtext(concat('[',group_concat(1),']'))
from seq_1_to_64;

Also use max_char_length() instead of max_length. This is a more
accurate length of characters. And add handling of empty string edge
case. Added testcases accordingly.

The change that uses max_char_length() causes side effects where
creating a table using a VEC_FROMTEXT(CHAR(1)) would result in a
0-dimensional vector field. This is accurate but 0-dim vector table
fields should not be allowed. So we make cases like this result in
a one-dimensional field.

Also fixed the underflow in (args[0]->max_length - 1) * 2 when the
arg's max length is 0. Previously this underflow would cause

create table t1 select vec_fromtext(NULL)

to fail with ER_TOO_BIG_FIELDLENGTH. Now it will be a VECTOR(1) field
add639919887...
add63991988734383c5e942de2a19c6c45f511f7
Alexander Barkov
MDEV-40790 SELECT INTO row_type_of.field crashes the server

The server crashed on DBUG_ASSERT on a SELECT into:
- a `ROW TYPE OF table1` field variable
- a `ROW TYPE OF cursor1` field variable

Fix:

- Adding a class my_var_sp_row_field_by_name
- Adding a method sp_rcontext::set_variable_row_field_by_name()
- Fixing the DBUG_ASSERT
9f27056cbae2...
9f27056cbae2f3c8e4db2dee37dd5fe1ca8c71a8
Oleksandr Byelkin
Merge branch 'bb-10.11-release' into bb-11.4-release
987a2a28977f...
987a2a28977f63f1d485b46ef6e3026df53e98aa
Oleksandr Byelkin
Merge branch 'br-11.4-merge' into bb-11.8-release
970492062d91...
970492062d91cd606dd3f6f8a52bd51cf746ab4f
drrtuy
chore: remove jemalloc extension from DuckDB CMake b/c since 1.5.4 is is a part of DuckDB core.
91156c3de587...
91156c3de58762196605150ab3f756fe952592d1
Alexander Barkov
MDEV-40639 Open SYS_REFCURSOR crash, if many cursors inside a function

Problem:

If:
- A routine A() opened a SYS_REFCURSOR with a function B() in the SELECT list
- The function B() also opened some SYS_REFCURSORs

Then reallocation of the cursor array THD::m_statement_cursors could happen
during the execution of B(), so all sp_cursor_array_element pointers inside
sp_instr_copen_by_ref::exec_core() of routine A() became invalid.

Fix:

Chaging the data type of sp_cursor_array:
- from Dynamic_array<sp_cursor_array_element>
- to Dynamic_array<sp_cursor_array_element*>

So now only reallocations of the array of cursor pointers happen,
while sp_cursor_array_element instances always stay on their originally
allocated memory positions.

Note:
sp_cursor_array_element instances are allocated using the standart C++ "new"
and deleted using the standard C++ "delete". Using a MEM_ROOT does not
seem to be relevant here.
8c62b52b24e6...
8c62b52b24e63e8edc73b87ed1f7abe82ef046d0
Daniel Black
MDEV-40801 ppc64le ro_after_init isn't pagesize aligned

Align ro_after_init using MAXPAGESIZE instead of COMMONPAGESIZE.

COMMONPAGESIZE may be smaller than the actual page size supported by
the target ABI. This can leave ro_after_init sharing an OS page with
adjacent sections, causing mprotect() to change permissions on data
outside ro_after_init.

Use MAXPAGESIZE so the section boundaries are aligned to the maximum
page size required by the target linker/ABI.

This is particularly important on architectures such as ppc64le and
aarch64, where the runtime page size can differ from COMMONPAGESIZE.

Before:
  .data          0x...1b80000
  ro_after_init  0x...1c70000
  .bss          0x...1c72000

After:
  ro_after_init starts and ends on MAXPAGESIZE boundaries, ensuring
  mprotect() only affects pages belonging to ro_after_init.

Co-authored-by: ChatGPT GPT-5.6 Luna <[email protected]>
84695e9c0b76...
84695e9c0b762db7ce7e23fc4ac51717b3a77efc
Daniel Black
MDEV-40243 Fix MEMORY_LEAK_C leaks in mariadb-dump  (rockdb tests)

With memory leaks fixed in the rocksdb.mysqldump/mysqldump2 no
longer need to run with leak detection disabled.

There tests are still disabled as there's no --rockdb arg to
mariadb-dump, but removing so there's no precidence to ignoring
leaks.

ref: 2217477fb8fc82f4921d9d13afcd24b1d86b34d6
81bb68ba63b5...
81bb68ba63b59ec5999afea7b1182350761d4de9
drrtuy
chore: add DuckDB version info function.
79520ba4e5b1...
79520ba4e5b17ac69f69a980615ad81f26f6b975
Daniel Black
RocksDB: compile fix std::replace requires algorithm header

Otherwise it compile fails.

Found in clang-24.
790a084aca40...
790a084aca40a3700a14cf3f98de7f3159957e76
drrtuy
feat: update DuckDB submodule to 1.5.5.
77c8f7916181...
77c8f791618136002e5724ca81f365134b583a29
Daniel Black
MDEV-40749 period.create test leaks/faults in asan

Selecting from the information_schema.plugins causes the loading
of all plugins. Because rockdb leaks, and duckdb triggers an
address sanitizer warning on shutdown avoid this table.

Use the information_schema.ENGINES to validate that InnoDB is
disabled per the original request in the review of MDEV-32205.
6b8e55a8824b...
6b8e55a8824b66ed3a0af20c3d64bf6e3556df62
Oleksandr Byelkin
Merge branch '12.3' into bb-12.3-release
64c19f15160b...
64c19f15160bc4fc796c25037c31b579a14e0c9b
Oleksandr Byelkin
Merge branch 'bb-11.8-release' into bb-12.3-release
5b9200a2896e...
5b9200a2896e22caaa782a3bfd67677554444bcb
Oleksandr Byelkin
fix merge
53b1cc014932...
53b1cc0149328c7d3857d9d0d6efbbbc779ac2c2
Alexander Barkov
MDEV-28498 Incorrect information in file: './test/t0.frm' on CREATE TABLE

Applying HEX encoding write writting an ENUM/SET TYPELIB to FRM
if the TYPELIB has 0x00 bytes in the value.

This HEX encoding was earlier used only to write UCS2/UTF16/UTF32 TYPELIBs.

A new flag FIELDFLAG_FRM_HEX_ENCODED_TYPELIB was added to indicate
that the TYPELIB is hex encoded. It's used only inside FRM.
Note, it's mangled with FIELDFLAG_TREAT_BIT_AS_CHAR.
This should not be harmful:
- BIT and ENUM/SET columns are handled by two separate code branches
  when opening an FRM
- The flag is unset immediately after decoding TYPELIB, so the rest
  of the code does not se an unexpected flag combination.
4936dbe51970...
4936dbe5197065496aad913c3f9f4cba7bf69700
Yuchen Pei
MDEV-40168 wip

works:

create table t1 (c int, j json, key idx ((CAST(j->'$.tags' AS CHAR(6) ARRAY))));
Warnings:
Note 1071 Specified key was too long; max key length is 1000 bytes
SHOW CREATE TABLE t1;
Table Create Table
t1 CREATE TABLE `t1` (
  `c` int(11) DEFAULT NULL,
  `j` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL CHECK (json_valid(`j`)),
  `DB_MVI_1` blob GENERATED ALWAYS AS (json_extract(`j`,'$.tags')) STORED,
  KEY `idx` (`DB_MVI_1`(1000))
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci
DROP TABLE t1;
3ad0455a2651...
3ad0455a2651a993b3cd8dfceeb893bfb1218a0e
Georgi (Joro) Kodinov
MDEV-40661: mysql_upgrade.test not stable on a busy server

The cleanup of the old connection goes on in the background.
It can take longer on a busy server and this triggers the active sessions
warning in DROP user.
Stablizied the test by disabling the warnings.
387e9af84621...
387e9af8462114215ee8499636e873522c3704c1
ParadoxV5
MDEV-40544 Assertion fail / Memory leak in `mariadb-binlog --force-read`

A checksum error in
`mariadb-binlog --verify-binlog-checksum --force-read` previously
resulted in both an error message and an Unknown event substitute,
the latter of which failed an assertion in debug builds or
became forgotten (memory leak) in non-debug (release) builds.

Since `mariadb-binlog --force-read` outputs “Unknown event”s
rather than errors in other invalid event cases,
this commit removes the error status from this situation to match.

Reviewed-by: Kristian Nielsen <[email protected]>
28f47d8948ea...
28f47d8948ea255dde3902e3f39ddf1303b90662
Oleksandr Byelkin
Merge branch '11.4' into br-11.4-merge
282a10a4a795...
282a10a4a7958fd11dcf98a6575664a3aa57ea21
Daniel Black
MDEV-38405 Assertion `tbl->trn == 0' failed in _ma_set_trn_for_table

Aria bulk insert operations disables share->now_transaction meaning
a concurrent open of the stable table will have
trn == &dummy_transaction_object for its MARIA_HA object during opening.

As the _ma_set_trn_for_table is setting the trn, its harmless if the
current trn is the dummy_transaction_object.

Relax the assert to allow for this state.
245e5c89368f...
245e5c89368f9ae14c14ebab7375da5c83c8e7b8
Marko Mäkelä
Document Sql_cmd_backup::execute()
1f11614ce75c...
1f11614ce75c6a49db3ef9bddb951bb0e1c8671f
Oleksandr Byelkin
Merge branch 'bb-11.4-release' into bb-11.8-release
1a052f27e374...
1a052f27e374fc9b4cb5b1fd098cf10f0e1381cc
Sergei Golubchik
rocksdb: don't abort early in submodule update

Fix for 1fb075512a7aeab8646a163cbb6f265c49f4c075 to allow
the ADD_SUBMODULE to perform updates.
18fce8e1e76a...
18fce8e1e76a5798ac9bf0a9a615b97175e8351a
Sergei Petrunia
MDEV-40738: main.cte_update_delete missing DROP VIEW v1, refers to wrong MDEVs.

Fix the testcase.
18a1f709e3ca...
18a1f709e3ca3ed5c2ea8efdc6065880ae16e053
Oleksandr Byelkin
fix windows
12ceb4d6aac1...
12ceb4d6aac1c287f4e2bf8d0412795f4e539020
Daniel Black
MDEV-34482 main.events_processlist test fix

As the test result is dependent of SHOW PROCESSLIST output,
adjust the wait condition to ensure the state is in sleeping
rather than "init" or another state.
128c7b41d0c0...
128c7b41d0c0497e84aee806e59c3133c59dc17c
Oleksandr Byelkin
Merge branch '10.11' into bb-10.11-release
0c2a964437c3...
0c2a964437c3283b075734373a4fca4cb89300f3
Oleksandr Byelkin
Merge branch 'br-10.11-merge' into bb-11.4-release
BuildBot (0.8.9) working for the MariaDB project.
Page built: Fri 21 Aug 2026 09:06:41 (UTC)