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
fc15162aa22a...
fc15162aa22a3b3849152458b03c8f3821ad4b9b
Lawrin Novitsky
Merge branch 'odbc-3.1'
fa03ebe5c407...
fa03ebe5c407f6bab5b018ffd1bda7ca62f929b7
Sergei Petrunia
MDEV-38072 Optimizer choosing the wrong plan: Part 2

Add OPTIMIZER_ADJ_FIX_ORDER_BY_INDEX_CHOICE flag to control the fix.

In test_if_cheaper_ordering(), switch to making choice between
indexes that provide ordering based solely on access costs.
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.
e6b8cacfb99e...
e6b8cacfb99ec4da1e759147987150afcfb3644b
Marko Mäkelä
Merge 11.4 into 11.8
d6b0a6f7eb22...
d6b0a6f7eb22cfc3b7d3dd75c639577ffc6a7807
Aleksey Midenkov
Compilation: writing to an object of type ‘ORDER’

/home/buildbot/amd64-last-N-failed/build/sql/sql_window.cc: In function ‘ORDER* concat_order_lists(MEM_ROOT*, ORDER*, ORDER*)’:
/home/buildbot/amd64-last-N-failed/build/sql/sql_window.cc:2976:13: error: ‘void* memcpy(void*, const void*, size_t)’ writing to an object of type ‘ORDER’ {aka ‘struct st_order’} with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]
2976 |      memcpy(copy, cur, sizeof(ORDER));
      |      ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/buildbot/amd64-last-N-failed/build/sql/field.h:29,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_class.h:32,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_acl.h:21,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_parse.h:19,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_window.cc:18:
/home/buildbot/amd64-last-N-failed/build/sql/table.h:236:16: note: ‘ORDER’ {aka ‘struct st_order’} declared here
  236 | typedef struct st_order {
      |                ^~~~~~~~
/home/buildbot/amd64-last-N-failed/build/sql/sql_window.cc: In member function ‘bool Window_funcs_sort::setup(THD*, SQL_SELECT*, List_iterator<Item_window_func>&, JOIN_TAB*)’:
/home/buildbot/amd64-last-N-failed/build/sql/sql_window.cc:3151:11: error: ‘void* memset(void*, int, size_t)’ clearing an object of type ‘ORDER’ {aka ‘struct st_order’} with no trivial copy-assignment; use assignment or value-initialization instead [-Werror=class-memaccess]
3151 |    memset(order, 0, sizeof(*order));
      |    ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/buildbot/amd64-last-N-failed/build/sql/field.h:29,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_class.h:32,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_acl.h:21,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_parse.h:19,
                from /home/buildbot/amd64-last-N-failed/build/sql/sql_window.cc:18:
/home/buildbot/amd64-last-N-failed/build/sql/table.h:236:16: note: ‘ORDER’ {aka ‘struct st_order’} declared here
  236 | typedef struct st_order {
      |                ^~~~~~~~
cc1plus: all warnings being treated as errors
make[2]: *** [sql/CMakeFiles/sql.dir/build.make:2640: sql/CMakeFiles/sql.dir/sql_window.cc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:10639: sql/CMakeFiles/sql.dir/all] Error 2
make: *** [Makefile:166: all] Error 2
c6b556cc04c8...
c6b556cc04c87ab21edd26450bc76ecb96b021ce
Lawrin Novitsky
One of tests had bogus dependency

Which somehow never popped up before as a problem.
bd98b9c211ff...
bd98b9c211ff8bcc3f99e42fc83da95955f0f6ba
Lawrin Novitsky
Trick to fix tests on macos-arm

Looks like tests and DM use different alignment and because of that 10th
paramemter of SQLSpesialColumns of type short gets read incorrectly by
the DM
b69cb60a83d1...
b69cb60a83d1da736f8594ecc11583430d3aac34
Christian Hesse
systemd: add missing quotes in examples

The line is commented, but let's have valid quoting anyway...
b2e23130a668...
b2e23130a66878833708c446f4507e13e4c3842d
Lawrin Novitsky
Fix of issue with iOdbc on ARM

We support iOdbc only on MacOS thus can be also formulated - ARM build on MacOS

The problem is that iOdbc does nto use exact type of ODBC function pointers fromt he driver,
but call them as variadic functions. That created different stack
parameters location - in fact only for 10th parameter of
SQLSpecialColumns function there 9th and 10th are 2 short parameters
going one after another.
To solve this we create this API function with different signature that
only reads parameters correctly and passes them to the function that
will process them.
b22473cf78ec...
b22473cf78eccacc7d7bdad483b670b522d6c08d
Daniel Black
MDEV-39158: Debian dh_installchangelogs parsing timestamp

Per policy[1] the date is meant to be a RFC 5322 type
timestamp.

[1] https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog
b07a36ee3295...
b07a36ee329569b9b2a4b373a1b16fe2dc3ed32a
Marko Mäkelä
Merge 10.11 into 11.4
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
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.
868ab472e6b0...
868ab472e6b097967b7e6338b1b0a07ee92ca249
Marko Mäkelä
Merge 11.8 into 12.3
840695801a0f...
840695801a0f2889abdd26c6c59509f99e15c966
Marko Mäkelä
MDEV-39170 innodb.mem_pressure,32bit fails with wrong result

In commit 36eba98817339f53cc57f1d4884ace3efb38db8d (MDEV-19123)
the test was changed but the result was not adjusted for
32-bit targets accordingly.
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
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.
734670b96279...
734670b96279ffd73e0996953c58156164c517fb
Alexander Barkov
MDEV-39115 `FUNCTION does not exist` error on package body assoc array variable

Problem:
When parsing `a.b()`, LEX::make_item_func_or_method_call() could not find
a package body variable 'a'.

Fix:
When searching for a variable, search not only in the current parse context,
but also in the parent package body context (if exists).
679add82a002...
679add82a002caf1fe84e6b108d5bd5669940ba2
Yuchen Pei
MDEV-39168 Do not force inline for xxhash functions in Debug builds

See https://github.com/Cyan4973/xxHash/issues/943

This fixes compiling errors like

inlining failed in call to ‘always_inline’ ‘XXH3_scrambleAcc_sse2’: function not considered for inlining
6660d0bdd7c8...
6660d0bdd7c8bdca9ec4e4e7e0f11df4e22c30f1
Sergei Golubchik
Merge branch '12.3' into 13.0

changed deprecation version for wsrep_slave_FK_checks,
because it was just deprecated this month
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])
6255b1953313...
6255b195331327cac64b2077728600a3c522f9d7
Aleksey Midenkov
MDEV-28619 fix
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.
47d1a0591fe6...
47d1a0591fe633357ced997efd55a19d6d1b0f1a
Georgi (Joro) Kodinov
MDEV-39123: Replace sprintf with snprintf in the InnoDB
binlog code

sprintf is deprecated (and triggers a deprecation warning) on some platforms,
saying it needs to be replaced with snprintf.
This is a good idea, since sprintf doesn't explicitly check the size of the buffer
it is printing to.
Fixed by adding an extra size argument to the helper function and making sure
this extra argument is passed down from the caller to snprintf.
43de3460bae3...
43de3460bae3033f4e1785c131e5437e192a12a1
Dearsh Oberoi
MDEV-38497 Remove all slave related configurations on RESET SLAVE ALL

Fix RESET SLAVE ALL to fully clear replica configuration of the
default unnamed slave, including SSL options, connection config,
logging info and group info so subsequent CHANGE MASTER starts
from a clean state.

Signed-off-by: Dearsh Oberoi <[email protected]>

Reviewed-by: Brandon Nesterenko <[email protected]>
Reviewed-by: Jimmy Hú <[email protected]>
Reviewed-by: Georgi Kodinov <[email protected]>
3d62dc272b68...
3d62dc272b682247191730ba88a4a39d756fe39a
rusher
[misc] use DOCKER_LOGIN as user if secret available

(cherry picked from commit 3b3623c0d3ebbf5625ed3598e5ef9e7bc26362f2)
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)
389210a6ab5a...
389210a6ab5a712a973ae63c1abb2ba9e6f9c88c
Thirunarayanan Balathandayuthapani
MDEV-39081 InnoDB: tried to purge non-delete-marked record, assertion fails in row_purge_del_mark_error

Reason:
=======
Following the changes in MDEV-38734, the server no longer marks
all indexed virtual columns during an UPDATE operation.
Consequently, ha_innobase::update() populates the upd_t vector
with old_vrow but omits the actual data for these virtual columns.

Despite this omission, trx_undo_page_report_modify() continues to
write metadata for indexed virtual columns into the undo log. Because
the actual values are missing from the update vector, the undo log
entry is recorded without the historical data for these columns.

When the purge thread processes the undo log to reconstruct a
previous record state for MVCC, it identifies an indexed virtual
column but finds no associated data.

The purge thread incorrectly interprets this missing data as a NULL
value, rather than a "missing/unrecorded" value. The historical
record is reconstructed with an incorrect NULL for the virtual column.
This causes the purge thread to incorrectly identify and purge
records that are not actually delete-marked, leading to abort
of server.

Solution:
=========
ha_innobase::column_bitmaps_signal(): Revert the column-marking
logic to the state prior to commit a4e4a56720c, ensuring all
indexed virtual columns are unconditionally marked during an UPDATE.

The previous "optimization" attempted to manually detect indexed
column changes before marking virtual columns. The manual check
for indexed column modifications is redundant. InnoDB already
provides the UPD_NODE_NO_ORD_CHANGE flag within row_upd_step().
This flag is being used in trx_undo_page_report_modify() and
trx_undo_read_undo_rec() should log or read virtual column values.

Refactored column_bitmaps_signal() to accept a mark_for_update
parameter that controls when indexed virtual columns are marked.
TABLE::mark_columns_needed_for_update() is the only place that needs
mark_for_update=true because only UPDATE operations need to mark
indexed virtual columns for InnoDB's undo logging mechanism.

INSERT operation is already handled by
TABLE::mark_virtual_columns_for_write(insert_fl=true).
Even the commit a4e4a56720c974b547d4e469a8c54510318bc2c9 changes are
going to affect TABLE::mark_virtual_column_for_write(false) and
It is called during UPDATE operation, and that's when
column_bitmaps_signal() needs to mark  indexed virtual columns.

Online DDL has separate code path which is handled by
row_log_mark_virtual_cols() for all DML operations
2fe072632e49...
2fe072632e49c1da19e19a155ff1f1f4d181b79a
Dmitry Shulga
MDEV-38561: ASAN heap-use-after-free in Query_arena::free_items/sp_lex_cursor::~sp_lex_cursor

On re-parsing of a failed cursor statement inside the stored routine,
the free_list of sp_lex_cursor could point to items placed on a dedicated
memory root that is created during re-parsing of the failed statement.

In result, when sp_head object is destroyed the mem_root created for
re-parsing the cursor's statement is de-allocated but the free_list
pointer of sp_lex_cursor still point to objects previously allocated
on this memory root.

To fix the issue, save the pointer to the cursor's free_list in
a data member of sp_lex_instr class and nullify it right after this
memory root be deallocated.
2f4743f1515d...
2f4743f1515d241ed0c903e376759291c9c41800
Alexandru Diaconu
MDEV-38791 TO_DATE() allows duplicate format specifiers

The Oracle-mode TO_DATE() function incorrectly parsed strings containing
conflicting format specifiers within the Day-name family (e.g., 'DAY DY')
without throwing an ER_STD_INVALID_ARGUMENT error.

This patch completes the existing validation framework for family-based
conflict checks in item_timefunc.cc during format string parsing.
Specifically, it adds formats_used() checks for FMT_DAY, ensuring that
specifiers within the Day-name family strictly block each other. This
aligns the Day-name handling with the already existing checks for the
Year, Month, Hour, and Meridian families.

Compatible specifiers, such as YYYY and DDD (Year and Day of Year),
remain unaffected and parse successfully. A comprehensive MTR test
suite has been added to func_to_date.test to cover standard and
edge-case conflicts.

Reported-by: Elena Stepanova <elenastepanova@github>

Signed-off-by: Alexandru Diaconu <[email protected]>
206074ec88f3...
206074ec88f32deea94a4a040c83864309f594ae
Mohamed
MDEV-38601 require FEDERATED ADMIN for SHOW CREATE SERVER

SHOW CREATE SERVER was accessible to any user with a global
privilege, without requiring FEDERATED ADMIN. Add a privilege
check before mysql_show_create_server() so that only users
with FEDERATED ADMIN can view server definitions.
1f95fe6fd378...
1f95fe6fd378c808c6805be6f1ba81a602eb049a
forkfun
MDEV-36183 mariadb-dump backup corrupt if stored procedure ends with comment

When a stored procedure, trigger, or event ends with a line comment (#comment
or --comment), mariadb-dump would append the custom delimiter (;;) on the same line.
This caused the comment to "comment out" the delimiter, leading to syntax errors
during restoration.

Fixed by ensuring a newline is inserted before the delimiter in the dump output.
0e074260511d...
0e074260511d19624f1ab8496640712b49acc6b4
Lawrin Novitsky
Parsec plugin was missing in tarballs and not compiled in on Windows
0bbec68242a9...
0bbec68242a9fa4c681993a895807cf077991790
forkfun
MDEV-32770 mariadb-dump produces not loadable dump due to temporary view structure

When mariadb-dump produces a dump, it first creates a temporary placeholder for views
to satisfy potential dependencies before their actual creation later in the dump file.
Previously, these views were populated with int literals for their columns (1 AS `col_name`).
This could cause syntax or type-resolution errors during restoration if another view depended
on this placeholder view.

This commit changes the placeholder column values from 1 to NULL, as it is more permissive
and allowing the dump to be restored successfully.
02aedc106596...
02aedc106596fe494b4fa408a627081319fbecad
Marko Mäkelä
Merge 11.8 into 12.3
02943077c50c...
02943077c50ccb19d05943de8f07d7c1cdb54c9d
Rex Johnston
MDEV-29360 Crash when pushing condition with always false IS NULL into derived

When a condition containing an always FALSE range part is pushed
down into a derived table, an enclosed outer reference can cause
a null pointer crash.  An example

SELECT * FROM (SELECT id  FROM t1 GROUP BY id) dt1, (SELECT id FROM t2) dt2, t3
  WHERE dt2.id = t3.id AND dt1.id BETWEEN 0 AND (dt2.id IS NULL);

is considered as one that can be pushed into the derived table dt1
because the expression (dt2.id IS NULL) is identified as always false.
On the on other hand the condition still contains a reference to a
column of the table dt2. When pushing the condition to the where clause
of the derived table dt1 a copy of it is created and this copy is
transformed to be used in the new where clause. When the transformation
procedure encounters a reference dt2.id it crashes the server as only
the references to the columns used in the group by list of the
specification of dt1 or those equal to them are expected in the
condition that can be pushed into the where clause of the derived table.

The fix here is transform the argument to the function Item_func_isnull
from something that may be a column reference, but cannot be null to
an Item_literal that also cannot be null (1).

Based on patch by Igor Babaev.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Sat 28 Mar 2026 16:55:00 (UTC)