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
fedc3c6d8a03...
fedc3c6d8a034584ff3cd4d85fa5e56ef431edc4
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
fd6c23d0b864...
fd6c23d0b864e285ef5fbafdd61127b93e7eb8e1
Sergei Golubchik
MDEV-40445 TLS session resumption

in fact it was already on in the server, so this only
enables statistics to see it in SHOW STATUS, adds tests,
and updates C/C to match.

Assisted-By: Claude:claude-5-opus
f4299f0bbf38...
f4299f0bbf38820794295bd4cae427544681cbd1
Georgi (Joro) Kodinov
MDEV-39718: Produce Markdown plugin API documentation

Generated the plugin API headers using a shell script.
Fixed some doxygen comment mistakes in the headers.
Added a cmake conveninence target to generate the docs into $BUILD_DIR/docs
Added a main page for the API docs.
Included all of the existing group .md files into the CMake target
Leveraged moxygen 2.1.11's fixes to produce the full API docs in a single go
Removed the list of output .md files from the CMake target and switched to a
stamp file to avoid unnecessary rebuilds of the docs when the list of .md
files changes.
Addressed various review comments.
eaab31815e07...
eaab31815e0749832419d01e730b1f1e9919e157
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.
ea7c45ec2fbc...
ea7c45ec2fbc8cf9882ab745ff84a81c5f4b6af3
Sergei Petrunia
Move parallel func declarations from sql_select.cc to sql_parallel_workers.h
e8612dd77edc...
e8612dd77edc9b9c7a7fa29522f448ee5a58fba9
Sergei Petrunia
Make compile (todo: sync with comments)
e6e8f6ae9a56...
e6e8f6ae9a5608d6202af993f11b25f23409f691
Monty
Fixed wrong error handling in handler::ha_update_row()

- Error could be wrongly ignored
dee6ce030d65...
dee6ce030d653107eb72fbd89a2e0eab7bdcc0ab
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
dd6c4b656265...
dd6c4b656265d161d9a3b93330e609bd02f63470
Monty
Added proper cleanup of main.cte_update_delete.test
da18481158c8...
da18481158c81ca94689702073c3e04aad85a6a3
Georgi (Joro) Kodinov
Addendum to MDEV-20749's fix: addressed Kristian's comments on indenting and #ifdef-ing.
c3b87567482c...
c3b87567482c4a307996f6b42deaca1e41943239
Alexander Barkov
MDEV-39563 Implement UPDATE ... RETURNING ... INTO
bd370311c47d...
bd370311c47ddd9ed8051826e14acc1249e1c1f9
Lawrin Novitsky
ODBC-504 Catalog functions did not snitize parameters(length)

All but SQLTables did not check if name parameters are too long. That
could cause buffer overwlows.
The testcase has been added.
b33e137d0590...
b33e137d0590d3e372435202ddf443c345007432
Yuchen Pei
MDEV-40751 Make sure that VEC_FROMTEXT results in a length of multiple of 4
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
aab200ac99f9...
aab200ac99f9aed4ee88815b0d0fb8da96af3225
Georgi (Joro) Kodinov
MDEV-39718: Produce Markdown plugin API documentation

Generated the plugin API headers using a shell script.
Fixed some doxygen comment mistakes in the headers.
Added a cmake conveninence target to generate the docs into $BUILD_DIR/docs
Added a main page for the API docs.
Included all of the existing group .md files into the CMake target
Leveraged moxygen 2.1.11's fixes to produce the full API docs in a single go
Removed the list of output .md files from the CMake target and switched to a
stamp file to avoid unnecessary rebuilds of the docs when the list of .md
files changes.
Addressed various review comments.
a9dd9e21a993...
a9dd9e21a9934bc13811bdd21813f813843dec1f
Aleksey Midenkov
MDEV-40799 Runtime plugin/UDF load errors lost under --silent-startup

Regression from MDEV-32745 (7828fb475b0), which guarded the
plugin-load my_error() calls with opt_silent_startup.  That option is
a lifetime global, set once at startup and never reset, so the guard
suppressed the SQL error for the whole server lifetime, not just
during startup.  Runtime operations (INSTALL PLUGIN, CREATE FUNCTION
... SONAME) then skipped my_error(), never set the diagnostics area
and wrongly succeeded - e.g. main.ps's "call proc_1()" no longer
failed with ER_CANT_OPEN_LIBRARY.

Startup callers pass MYF(ME_ERROR_LOG); runtime callers pass MYF(0).
Gate the silencing on that flag via silent_plugin_startup() so it
applies only to the startup error-log path, and runtime errors always
reach the client.

No new test case: the runtime failure path is already covered by
existing tests (e.g. main.ps's ER_CANT_OPEN_LIBRARY check).  The
regression stayed invisible only because stock MTR does not start
servers with --silent-startup.  A dedicated test would have to restart
the server with --silent-startup solely to assert that a startup-only
option does not affect runtime, which adds little over the restored
invariant.
a716775025d1...
a716775025d134c0c0882915ed5dc9d191878c9e
PranavKTiwari
MDEV-36990: SIGFPE in get_max_range_rowid_filter_elems_for_table
Problem:
A zero-length column (CHAR(0), VARCHAR(0), BINARY(0), VARBINARY(0)) was accepted as a PRIMARY KEY column.  The resulting zero-length key part left ref_length == 0, causing a division by zero in get_max_range_rowid_filter_elems_for_table().

Cause:
init_key_part_spec() rejected a zero-length key part only when the column had NOT_NULL_FLAG.  A PRIMARY KEY column becomes implicitly NOT NULL only later, in the key loop of mysql_prepare_create_table_finalize(), so at validation time the flag is still clear.

Fix:
Reject a zero-length key part also when key.type == Key::PRIMARY. Nullable zero-length columns remain indexable by non-unique and UNIQUE keys.
a7071840d689...
a7071840d689ff2336e8bb9e22056071a246d11a
Marko Mäkelä
Clean up innodb_backup_batch_wait()
a591f33cb4a7...
a591f33cb4a70d9c4fb009382d86f0b8018735a8
Yuchen Pei
MDEV-40751 Make sure that VEC_FROMTEXT results in a length of multiple of 4
a2020ca6c216...
a2020ca6c21691a3727fa2e6a5b8524242e93836
Marko Mäkelä
fixup! 293f0166f3c91ab22e25ab4997b452c91a79c1a9
933b5e17980b...
933b5e17980b013efe9dc25b0375c17c66f89a52
PranavKTiwari
a
6c7d9565dd44...
6c7d9565dd448504a7e2e2c725f215853c10bccd
Monty
Removed wrong assert on thd->lex->query_tables != table_list

This was in log_event_server.cc and I got mutiple asserts on this
in valgrind builds, when malloc() returned same address for different
table list (with free() in between)
6bcf1fa6aef5...
6bcf1fa6aef5557f2571634653a0e3805fe657c3
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
67cba6e24303...
67cba6e24303c8ae910fe53427276f80a0607fe4
KhaledR57
MDEV-40498 KEY_OP_CHANGE copies length without checking header_end

The KEY_OP_CHANGE branch of _ma_apply_redo_index() passed the length from
the redo record to memcpy() without checking it against the end of that
record, and bounded the destination with a DBUG_ASSERT, which is compiled
out when DBUG_OFF is set. A record claiming more data than it carries
could therefore copy bytes of earlier records into the page, and an
unchecked page offset could put that copy outside the page.

Turn the assert into a runtime check. The logged length and its two
operand bytes must fit in what is left of the record, the page offset
must be set, and offset plus length must stay inside the used page. The
page bound matters on its own: page_offset comes from KEY_OP_OFFSET,
which is still guarded only by a DBUG_ASSERT, and records carrying no
KEY_OP_SHIFT reach the copy with no bound on it at all.

The test forges the logged length with corrupt_change_length and the
logged offset with corrupt_change_offset, then crashes the server so
recovery has to replay the records. Each keyword uses the largest value
the earlier checks accept, so the two cases trip different halves of the
new check.
61d34a8ea300...
61d34a8ea300765317df0e8631f70bcf7e0947c6
Aleksey Midenkov
MDEV-40799 Runtime plugin/UDF load errors lost under --silent-startup

Regression from MDEV-32745 (7828fb475b0), which guarded the
plugin-load my_error() calls with opt_silent_startup.  That option is
a lifetime global, set once at startup and never reset, so the guard
suppressed the SQL error for the whole server lifetime, not just
during startup.  Runtime operations (INSTALL PLUGIN, CREATE FUNCTION
... SONAME) then skipped my_error(), never set the diagnostics area
and wrongly succeeded - e.g. main.ps's "call proc_1()" no longer
failed with ER_CANT_OPEN_LIBRARY.

Startup callers pass MYF(ME_ERROR_LOG); runtime callers pass MYF(0).
Gate the silencing on that flag via silent_plugin_startup() so it
applies only to the startup error-log path, and runtime errors always
reach the client.
584a1a36893d...
584a1a36893d3bf8476c4a26b6f7a54a1fb1287d
PranavKTiwari
MDEV-36438- Added test case mentioned in this MDEV to validate the changes done as part of MDEV-36990
508c1cd9d76c...
508c1cd9d76c1677986a21f5f3d096bf6891a077
Sergei Golubchik
MDEV-40445 TLS session resumption (wolfssl)

* enable HAVE_SESSION_TICKET to allow resumption
* enable OPENSSL_ALL+KEEP_PEER_CERT to keep peer cert in the ticket,
  otherwise REQUIRE SUBJECT doesn't work after resumption
* disable OPENSSL_EXTRA which was enabled as a replacement
  when OPENSSL_ALL was disabled in 136e8661197
* disable NO_WOLFSSL_STUB to get SSL_CTX_sess_hits/etc stubs
* but they're stubs, always return 0, so add a wolfssl combination to
  the test that checks for these values
470b5866ce33...
470b5866ce3356ee6b8bb82172922147c9be262a
Thirunarayanan Balathandayuthapani
MDEV-40776 Atomic CREATE OR REPLACE silently breaks the foreign key


Problem:
========
Atomic CREATE OR REPLACE renames the original table to a #sql-create- backup
copy, and because such a name is not treated as a temporary name, InnoDB
renamed every constraint of that table, including SYS_FOREIGN.REF_NAME of the
constraints that belong to other tables. Those constraints ended up
referencing the backup copy, which is dropped at the end of the statement, so
the child tables were left with a dangling reference that survived a restart.

Solution:
============
row_rename_table_for_mysql(): Fix this by splitting the two halves of the
constraint renaming. Identifiers that the renamed table owns
(SYS_FOREIGN.ID, FOR_NAME, SYS_FOREIGN_COLS.ID, and REF_NAME of a
self-referencing constraint) keep following the table, so that they cannot
conflict with the constraints of the table that is created under the original
name, while REF_NAME of the constraints of other tables is left pointing to
the original name, so that the newly created table inherits them and is
rejected if it is not compatible with them.

dict_table_rename_in_cache(): Does the same in the data dictionary cache
by detaching the referencing constraints from the backup copy
instead of renaming them, so that dict_load_foreigns() attaches them to
the new table.

As the newly created table can now be a parent table, the tables that
CREATE OR REPLACE drops in order to restore the previous state must be
dropped without foreign key checks, both in drop_open_table() and in
the DDL log recovery (execute_drop_table()).
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.
3523ffdf971f...
3523ffdf971f60d8d91f571618c768057fae4632
sjaakola
MDEV-36677 rsync sst fails with different innodb_log_group_home_dir and datadir

Backported the fix done by Pekka Lampio for mariaDB 11.4 in PR
https://github.com/mariadb-corporation/codership-mariadb-server/pull/543

The PR has a fix for wsrep_sst_rsync script and new mtr test:
galera_3nodes.galera_mdev_36677" to check that the rsync SST method of Galera
works correctly also when the joiner node store InnoDB log files in a dedicated
directory separate from the data dictionary

Note: merging this PR to 11.4 may not be fully functional as there are other
changes in the rsync SST script. Take a look at the original 11.4 PR when merging.
3496f1607305...
3496f16073051a5afc288ce518e2b01a0273d531
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
33280889dd35...
33280889dd359b5d0f19962958d26fb2a501e307
sjaakola
MDEV-38243 Write binlog row events for changes done by cascading FK operations

Fixes according to Kristian Nielsen's review:
* Removed obsolete checks for slave thread
* Supporting slave with old MariaDB version.
  Events logged in cascade operation are additionally flagged with
  the long-standing NO_FOREIGN_KEY_CHECKS_F, so a replica that does
  not understand FK_CASCADE_EVENTS_F still disables foreign key checks
  and  does not re-execute the cascade

Also, thee are now binlog event flags to mark both original and derived
events. This will make it possible for the slave to choose whether to use
the derived events in applying or to execute the cascade operation

There is a new test rpl.rpl_fk_cascade_binlog_row_old_slave, for checking
compatibility with replication slave of old mariadb version
2df7bb670607...
2df7bb67060780198fef333954721ef2d4d9dfb3
sjaakola
MDEV-38243 Write binlog row events for changes done by cascading FK operations

Refactoring according to Serg's review. In this version, SE/server API now
narrows the SE role to just report the changes done by foreign key cascading,
and server side does most of the work after that.

Added a design document MDEV-38243-design.md
2a78b100fa82...
2a78b100fa825f16728a323b6f607d4e8cc8ffea
sjaakola
MDEV-38243 Write binlog row events for changes done by cascading FK operations

This commit implements a feature which changes the handling of cascading foreign
key operations to write the changes of cascading operations into binlog.
The applying of such transaction, in the slave node, will apply just the binlog
events, and does not execute the actual foreign key cascade operation.
This will simplify the slave side replication applying and make it more predictable
in terms of potential interference with other parallel applying happning
in the node.

This feature can be turned ON/OFF by new variable:
rpl_use_binlog_events_for_fk_cascade, with default value OFF

The actual implementation is largely by windsurf.

The commit has also mtr tests for testing rpl_use_binlog_events_for_fk_cascade
feature:  rpl.rpl_fk_cascade_binlog_row, rpl.rpl_fk_set_null_binlog_row and
rpl.fk_cascade_binlog_row_rollback
2a3891f1b7e1...
2a3891f1b7e1993e1de3bc43242d87f5ff0a2be4
Alexey Yurchenko
Merge branch '10.11' into MDEV-38147-missing-result-file
2129804256ba...
2129804256bab82788c3a7f336649afb43984212
monthdev
MDEV-20749 Improve mysqlbinlog --flashback error reporting

Handle corrupted row events by reporting whether the field length could
not be determined from metadata or whether the field extends past the
row buffer instead of falling out through debug-only assertion paths
or ad hoc exits during flashback row conversion. Propagate flashback
conversion failures through the normal mysqlbinlog error path so debug
builds produce the intended diagnostics cleanly.

Add replication tests covering corrupted BLOB metadata and corrupted
BLOB length prefixes using server-side debug injection to write broken
binlog contents and mysqltest-friendly mysqlbinlog invocation patterns.

Reviewed-by: Brandon Nesterenko <[email protected]>
Reviewed-by: Georgi Kodinov <[email protected]>
12016fdeedf7...
12016fdeedf771099059e367bf41a4bf4066b471
Alexey Yurchenko
MDEV-38147 add missing result file for MDEV-38147_gtid_off test
0f07d75824b9...
0f07d75824b9c282005d94adeb590905cf4c9c4e
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
0bcefd01403e...
0bcefd01403e925259a9fe00deabf52fce8163ea
Monty
Removed some not needed checks and a DBUG_ASSERT() for not covered code

- In ha_partition.cc:check_parallel_search(), remove check if
  item_field->field is null. This is not needed as the function is run
  after fix_field() which guarnatees that the field is always set.
- Added DBUG_ASSERT(new_field) to Item_field::fix_fields() to check if a
  select-list item, found by name or alias when resolving ORDER BY/GROUP
  BY/HAVING, can have field == 0. This error path is not covered by any
  mtr test.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Mon 17 Aug 2026 22:42:12 (UTC)