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
eef2f27c0a78...
eef2f27c0a78df3b2b5c45aa2bb7be3ed21a1acd
Sergei Golubchik
MDEV-40186 MEMORY tables incorrectly restart index scan on DELETE

remember the last found key and restart the search (if needed)
from it not from the original one.
ecd9b892d843...
ecd9b892d8433127d8ee758d90e69479c07ba062
Alexey (Holyfoot) Botchkov
MDEV-39683 Numeric aggregates should end up with an error for xmltype.

Appropriate xxx_fix_length_and_dec() added to the Type_handler_xmltype.
e7eeb57cc86c...
e7eeb57cc86c2cafdb463bb4bdb693103b777902
Sergei Golubchik
MDEV-39318 some MTR tests fail with --ssl

* many test expected error 2013 (CR_SERVER_LOST)
  they should also expect 2026 (CR_SSL_CONNECTION_ERROR)
* some test --connect and expect a specific pre-auth error,
  they should use NOSSL option
* some tests start with invalid certificate - they work because
  mariadb-test doesn't connect with ssl by default. With --ssl
  it does and simply cannot connect. These tests use include/not_ssl.inc
* ssl_cipher restarts the server internally with invalid cipher.
  it should reconnect the default connection without SSL, otherwise
  mariadb-test will fail to connect after server is restarted
* tests that print ssl status without forcing it first - shouldn't,
  they don't know whether ssl is enabled or not.
* some perfschema tests are socket-specific and use include/not_ssl.inc
* perfschema status tables had too small column for ssl_ciphers value.
  Fixed as in f34afeaf6b83 (MDEV-39318)
e749b8e678cc...
e749b8e678cc253fb1f9b12157bb4ee6b6112e9c
Georg Richter
Merge branch '3.3' into 3.4
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
e085c5b1fc6b...
e085c5b1fc6b274f7bb36b1c10459ffd5020cc24
ParadoxV5
MDEV-40270 @@default_master_connection does not convert character sets

`Item::val_str()` doesnÂ’t specify the collation of the returned string,
yet `Sys_var_session_lexstring::do_check()`
(for `@@default_master_connection`) and `Sys_var_debug_sync::do_check()`
(for `@@debug_sync`) assume the `@@character_set_system` collation.

This commit replaces `Sys_var_debug_sync::do_check()`
with a delegate to `Sys_var_charptr::do_string_check()` to match
`Sys_var_dbug::do_check()`, as neither of those have this bug.
It ports the character set conversion to
`Sys_var_session_lexstring::do_check()` rather than delegating,
so the length check is not after a memory allocation;
this class has been refactored away in 11.3 (Commit 6151bde48c) anyway.
d1c05816c703...
d1c05816c703b30c8e3f86e1a42f9b49c9cf54b9
Sergei Golubchik
MDEV-39654 schema-qualified unquoted table name starting with digit fails to parse

add tests
d0ed68b97c32...
d0ed68b97c328cb3cd79bb0efa1ca40761e384de
Yuchen Pei
MDEV-40088 [to-squash] Disallow subqueries in INTERVAL clause in range interval auto partitioning

This is consistent with system time (versioning) partitioning. Also
consistent is that both allow expressions otherwise.
c7220a42d275...
c7220a42d275898d2eb1484e269fbf498a8e5cf9
bsrikanth-mariadb
MDEV-39916: Crash with having filter when being pushed down

When Item_func_not::fix_fields() is invoked, there are several instances where
ref argument being passed is NULL. One such instance is from the method
st_select_lex::pushdown_from_having_into_where().

Since a null ref is being accessed, a crash occurs.

This PR fixes the problem by adding a null check inside
Item_func_not::fix_fields()
c57f17f5af0f...
c57f17f5af0f5516ce57d6d5e923969ea63de694
Daniel Bartholomew
bump the VERSION
bf580f1d682e...
bf580f1d682e92b61230b981a7ee6f0f7f22900c
Sergei Golubchik
.gitignore plugin/auth_pam/testing/mariadb_mtr
b91f24674d78...
b91f24674d7892b00f59ef92ea49cd097a452f7c
Dave Gosselin
MDEV-28509: Dereferenced null pointer of type 'struct JOIN_TAB' in add_key_field

This patch fixes a crash when calculating join statistics during query
optimization for queries with an unused WINDOW definition.  Put another
way, the system may crash when a query defines a WINDOW but doesn't then
refer to it.

Item::marker is overloaded for different uses, many of which treat it as
a bit field.  However, the setup_group function uses it to mark that a
field was found when traversing a GROUP BY.  Originally, this marking
set the Item::marker field to 1 to indicate that it was found.  Later
on in setup_group (and only when SQL mode ONLY_FULL_GROUP_BY is
enabled), we would skip any such marked fields when checking that
fields only referenced those found in the GROUP BY; otherwise, it would
be silly to find fields of the GROUP BY within the GROUP BY field
itself.  Setting Item::marker to 1 seemed mostly harmless at that point
in time.  But later, in git sha 4d143a6ff6, we introduced several
changes: (1) the value of marker in setup_group was changed from 1 to
UNDEF_POS, (2) Item::marker was changed from uint8 to int8 (which has
since been changed to an int), and (3) UNDEF_POS which is defined to be
-1 was also added.

Queries that define WINDOWs internally will setup groups and orders as
part of query processing via the setup_group function.  Consequently
because of the behavior described earlier above, such queries may have
items with markers as UNDEF_POS (-1, or 0xffffffff) which is the same
as marking all of the flag bits as set.  This is disastrous for those
users of Item::marker which refer to it as a bit field, because every
flag bit appears set at once, including bits that are mutually
exclusive in meaning.  Even a masked test such as marker &
SUBSTITUTION_FL returns true when marker is -1.  In particular, the
method Item_direct_view_ref::grouping_field_transformer_for_where then
treats the ref as flagged for substitution and takes the wrong
execution path, leading to the crash.

Upon return from the setup_group function, we set the value of the
marker flag to zero if we set it to -1.  This preserves the marker
behavior for 'full group by' (if configured) while not otherwise
allowing the marker flag state to leak outside of this function.
b8ea2ec7b027...
b8ea2ec7b027d87c28fc8a2943adab254b22e2ac
ParadoxV5
MDEV-40270 @@default_master_connection does not convert character sets

`Item::val_str()` doesn’t specify the collation of the returned string,
yet `Sys_var_session_lexstring::do_check()`
(for `@@default_master_connection`) and `Sys_var_debug_sync::do_check()`
(for `@@debug_sync`) assume the `@@character_set_system` collation.

This commit replaces `Sys_var_debug_sync::do_check()`
with a delegate to `Sys_var_charptr::do_string_check()` to match
`Sys_var_dbug::do_check()`, as neither of those has this bug.
It ports the character set conversion to
`Sys_var_session_lexstring::do_check()` rather than delegating,
so the length check is not after a memory allocation;
this class has been refactored away in 11.3 (Commit 6151bde48c) anyway.
b4852ece3ad9...
b4852ece3ad9a6468c3108fe6e7da5caa3b4f725
Alexey Yurchenko
MDEV-40179 Found N prepared transactions after mariabackup SST

With log_bin=ON a transaction is committed via two-phase commit (the
binary log is the second participant), so it passes through the InnoDB
XA-prepare state. While a donor is held in BLOCK_COMMIT for a mariabackup
backup, its parallel appliers (wsrep_slave_threads > 1) leave one or more
such writesets prepared-but-not-yet-committed, and the snapshot captures
them. On a freshly SST'd joiner nothing resolves these prepared
transactions: binlog crash recovery does not run (the joiner has no in-use
binlog to recover from), and the wsrep continuity-based commit is inactive
because wsrep_emulate_bin_log is FALSE when log_bin is ON. The leftover
prepared transactions then abort startup with "Found <N> prepared
transactions!". Note this does not depend on the prepared set being
non-contiguous - even a contiguous run aborts, because nothing commits
or rolls it back.

Rollback these transactions in xarecover_handlerton(). If rollback fails
flag error to cause unireg_abort().
a8f5021aa65b...
a8f5021aa65b2b74d6c41c765d350c8ecb20750a
Thirunarayanan Balathandayuthapani
MDEV-27569  Valgrind/MSAN errors in ha_partition::swap_blobs() for BLOB not in secondary index

Problem:
=======
On a partitioned table containing a BLOB/TEXT column, an ordered
index scan calls ha_partition::swap_blobs() for every buffered
row, because it is being called only when table has blob fields.

When the buffered row comes from a secondary index that does not
cover the blob (e.g. KEY(f2) on (f2,f1)), InnoDB's
row_sel_store_mysql_rec() populates only the templated columns.
The blob column's null bit and its value-pointer bytes in
table->record[0] are left uninitialized. The partition handler
memcpy() this record into rec_buf, then swap_blobs() evaluates
blob->is_null(), reading the uninitialized null bit leads to
"use-of-uninitialized-value".

Solution:
=========
row_sel_store_mysql_rec(): When the record is being stored
from a secondary index, seed the NULL bitmap of mysql_rec
from prebuilt->default_rec before populating the templated columns.
Columns present in the index template have their NULL bit rewritten
explicitly while the row is stored, so only the columns absent from
the template (the uncovered blob) rely on this seed.
default_rec marks such nullable columns as NULL and preserves the
reserved NULL bit, so the uncovered blob is now defined as NULL.

Because of this, ha_partition::swap_blobs() skips it via its
"!bitmap_is_set(read_set) || blob->is_null()" guard and
never calls Field_blob::cached()/get_ptr(). This avoids not
only the uninitialized null-bit read and the follow-on
uninitialized blob value-pointer read.
a4e54c979cfd...
a4e54c979cfdf23831e7cc1eef10a3ad21dbbdc3
Sergei Golubchik
Revert "MDEV-17677: Keywords followed by .number parsed as identifiers"

This reverts commit 895b28d6721eadfad0d47723fcc949eae75cf8cf.
a27701503a7e...
a27701503a7edd4eb5b379c5cc64ab080a642202
Yuchen Pei
MDEV-15621 [to-squash] Follow some gemini review comments
a1134529115f...
a1134529115fc34848246770f329d07c13b4eda9
Sergei Golubchik
MDEV-39841 handlersocket plugin default secret is empty

if handlersocket_plain_secret is not specified, generate a random one.
one can still set an empty secret in my.cnf if needed.
9e907f89ae52...
9e907f89ae52435e58678b1bf785165e56ee1eb5
Yuchen Pei
MDEV-31182 Check for blob too in create_key_parts_for_pseudo_indexes

BLOB and VARCHAR has keys prefixed with length of the payload. This
length data itself has length HA_KEY_BLOB_LENGTH which is 2, as
demonstrated for example in Field_blob::set_key_image and
Field_varstring::set_key_image.

In this patch, when preparing key info for a range analysis, we
account for this extra HA_KEY_BLOB_LENGTH in the total key length for
BLOB. Previously it was only done for VARCHAR. This way, when doing
the actual range analysis, LIKE (Item_func_like::get_mm_leaf) can
correctly identify that it is dealing with a BLOB, thereby allowing
the space of 2 for the length data. This avoids later
Field_blob::set_key_image reading the payload as length data and
causing reading the wrong memory segment for the payload.
9a38407bbc68...
9a38407bbc68df8261544aa44ef18d334146f1cd
Vladislav Vaintroub
MDEV-37499 Crash in check_grant() on SHOW STATUS with a subquery using a CTE

Table references parsed after a WITH clause have their database name
filled in only when CTE references are resolved at the end of parsing,
but SHOW commands never invoked this resolution, leaving the name NULL.
Resolve CTE references at the end of the SHOW rule, as other statements do.
9667ae463eef...
9667ae463eefa26c57e471fd2d1ddef5a9ff83d4
Rex Johnston
MDEV-39323 Fix Item_func_between::get_mm_tree()

Produced by Claude Code.
91d0342416f8...
91d0342416f800ab44f600fc54ed8abe38da7deb
Sergei Golubchik
MDEV-39363 Logical Bug in `NOT ( ... XOR ... )` Evaluation with Implicit Type Conversion

for 0.1f val_int() is 0, val_bool() is 1.
8f9f563b4042...
8f9f563b404225cab1fa03f6612cb9fced9d467a
Alexander Barkov
MDEV-39518 Allow prepared statements in stored functions in assignment right hand

Allowing prepared statements in stored functions when
a stored function is used in an assignment right hand.

Both DEFALT clause of a variable initialization and
the right side of the SET statement are supported:

  CREATE PROCEDURE p1()
  BEGIN
    -- case 1: DEFAULT clause
    DECLARE spvar1 INT DEFAULT f1_with_ps(); -- OK

    -- case 2: SP variable assignment statement
    DECLARE spvar2 INT;
    SET spvar= f1_with_ps(); -- OK
  END;

- The parser now does not reject PS statements in stored functions.
  PS applicability in stored functions is now detected as run time.
  Note, PS statements in triggers are still prohibited by the parser.

- Functions with PS do not acquire MDL locks on tables.
  They work like procedures in terms of table opening.

- Functions with PS are not replicated as a single `SELECT f1()` call.
  They are replicated per-statement, like procedures.
8f5242e95219...
8f5242e9521934ab88260059d519a4a30b1311bf
Yuchen Pei
MDEV-31182 Check for blob too in create_key_parts_for_pseudo_indexes

BLOB and VARCHAR has keys prefixed with length of the payload. This
length data itself has length HA_KEY_BLOB_LENGTH which is 2, as
demonstrated for example in Field_blob::set_key_image and
Field_varstring::set_key_image.

In this patch, when preparing key info for a range analysis, we
account for this extra HA_KEY_BLOB_LENGTH in the total key length for
BLOB. Previously it was only done for VARCHAR. This way, when doing
the actual range analysis, LIKE (Item_func_like::get_mm_leaf) can
correctly identify that it is dealing with a BLOB, thereby allowing
the space of 2 for the length data. This avoids later
Field_blob::set_key_image reading the payload as length data and
causing reading the wrong memory segment for the payload.
8edc43ee73dd...
8edc43ee73dd0f9198ce35075cb0aebd709a4c32
Yuchen Pei
MDEV-15621 [to-squash] Follow some gemini review comments
8da34620ac39...
8da34620ac3935814cc7f9ba30bb51a6e2070237
Daniel Black
MDEV-40275: plugins.auth_ed25519 test falky - dropped users with connection warning

The slow cleanup of disconnected connections means that they
may still be visible as the DROP USER is executed. Ignore these
warnings.
8d818e9333da...
8d818e9333da8d1920dff4c2c555957e827409e4
Daniel Bartholomew
bump the VERSION
85fd75cb62f4...
85fd75cb62f4dbd145633c224e66b5a93f327aa4
Yuchen Pei
MDEV-15621 Auto add RANGE COLUMNS partitions by interval

Allow auto partitioning by interval in PARTITION BY RANGE COLUMNS

PARTITION BY RANGE COLUMNS (col_name)
INTERVAL interval [AUTO]
(
  PARTITION partition_name VALUES LESS THAN (value)
  [, PARTITION partition_name VALUES LESS THAN (value) ... ]
)

where

- col_name is the name of one column of type DATE or DATETIME or
  TIMESTAMP

- at least one partition is supplied, and the highest partition cannot
  have MAXVALUE range

- INTERVAL interval is a positive time interval. it can be mariadb
  format or oracle NUMTODSINTERVAL/NUMTOYMINTERVAL format. Like
  versioning, the smallest unit is second, i.e. no subsecond like
  microsecond.

- DATE column cannot have interval with values less than a day

- Subpartitions are allowed, but restricted to existing subpartition
  types, i.e. [LINEAR] (KEY|HASH)

When performing one of the following DML statements on such a table,
it will first add partitions by the specified interval until the
partition covers the current time:

- INSERT
- INSERT ... SELECT
- LOAD
- UPDATE
- REPLACE
- REPLACE ... SELECT

Partition addition will not cause an implicit commit like DDL normally
does.

The partitions are named pN.

Otherwise the table behaves exactly the same as a normal RANGE COLUMNS
partitioned table.

Note that TIMESTAMP is not allowed as a type for PARTITION BY RANGE
COLUMNS otherwise.
8208883f634d...
8208883f634d623d2aeb08a1e408f6eded88f768
Yuchen Pei
MDEV-15621 [refactor] Partitioning cleanup

change p_column_list_val::fixed to a bool
remove redundant end label in partition_info::fix_column_value_functions
815930c287b5...
815930c287b52e4ea59ca4859c1bfed07fdf200e
Daniel Bartholomew
bump the VERSION
56decda592c5...
56decda592c5344413f19095ec375c55baa21419
Georg Richter
CONC-834: Fix poll timeout reset loop on EINTR signals

Ensure that pvio_socket_wait_io_or_timeout() tracks elapsed
time using CLOCK_MONOTONIC when poll() is interrupted by EINTR.
This prevents the timeout deadline from constantly resetting
forward when periodic application signals (like profilers)
are active.

Kudos to Shaohua Wang for finding this issue and providing
a fix!
  • cc-x-codbc-windows: 'dojob pwd if '3.4' == '3.4' ls win32/test SET TEST_DSN=master SET TEST_DRIVER=master SET TEST_PORT=3306 SET TEST_SCHEMA=odbcmaster if '3.4' == '3.4' cd win32/test if '3.4' == '3.4' ctest --output-on-failure' failed -  stdio
55bf62e85e87...
55bf62e85e87a668e6463fdb402ccf853fb883d9
Rex Johnston
MDEV-39323 Fix Item_func_between::get_mm_tree()

Produced by Claude Code.
53b17c332ead...
53b17c332ead128e5d17190304a11e38c2f0a9b4
Sergei Golubchik
MDEV-39821 heap-use-after-free in heap_rnext with tree indexes

heap_update() forgot to update key_changed
4e175d9f8239...
4e175d9f82394e1d1bfdb458b2a4f9e62caf2197
Daniel Bartholomew
bump the VERSION
4b28744d539f...
4b28744d539f54fde9a2df91e36f6fe52737136b
PranavKTiwari
MDEV-40167: GTT created with the InnoDB incorrectly accept FULLTEXT/VECTOR indexes
Problem:
GLOBAL TEMPORARY tables were not subject to the same option/index restrictions as session TEMPORARY tables. Several InnoDB and server-layer checks tested only tmp_table(), so GLOBAL TEMPORARY tables could bypass validation for VECTOR/FULLTEXT indexes, DATA DIRECTORY, KEY_BLOCK_SIZE, and ROW_FORMAT=COMPRESSED.

Cause:
global_tmp_table() was added as a separate predicate from tmp_table(), but not all temp-table checks were updated to test both, so GLOBAL TEMPORARY tables fell through to "permanent table" logic in several places.

Fix:
Added global_tmp_table() alongside tmp_table() at each affected check:

Reject VECTOR and FULLTEXT indexes on GLOBAL TEMPORARY tables.
Reject/warn on DATA DIRECTORY, KEY_BLOCK_SIZE, and ROW_FORMAT=COMPRESSED for GLOBAL TEMPORARY tables, with accurate wording in the DATA DIRECTORY warning.
Fixed zip_allowed and related ut_ad assertions to exclude GLOBAL TEMPORARY tables.
Fixed m_use_file_per_table in set_tablespace_type() to exclude GLOBAL TEMPORARY tables (also fixes m_use_data_dir).
GLOBAL TEMPORARY tables now validate the same as session TEMPORARY tables across these options.
4104275e78a6...
4104275e78a634181ac0ce440ca92c44144fcec9
Vladislav Vaintroub
MDEV-37493 I_S.ROUTINES stopped matching db name case-insensitively with lower_case_table_names=2

Since MDEV-14432, get_lookup_field_values() lowercases the WHERE value
only for lower_case_table_names=1, to preserve the letter case of table
names in I_S output. But mysql.proc.db is utf8mb3_bin and always stores
lowercase when lower_case_table_names is non-zero, so with
lower_case_table_names=2 the index lookup in fill_schema_proc() missed.

Fix: lowercase I_S lookup values for any non-zero
lower_case_table_names again. To show db and table names in I_S in
their on-disk letter case (MDEV-14432), resolve exactly-pinned names in
make_db_list() and make_table_name_list() with a new mysys function
my_canonical_case_name(), which returns the canonical name of the last
path component. Unlike before, the true name is now shown even when
the WHERE value uses a different letter case than the on-disk name.
385b1629bec8...
385b1629bec80db33979e2346275269fa520676d
Yuchen Pei
MDEV-40048 [to-squash] Allow trigger and LOCK TABLES to work with range interval auto partitioning

When a range interval auto partitioned table is the target of a
trigger, the triggering statement is not necessarily one that would
cause the auto-creation of new partitions, so we need to account for
that.

Also added support for LOCK TABLES ... WRITE.

Improved tests coverage by adapting tests from versioning.partition.
18f57d992e49...
18f57d992e4918ff12403bbba81922b8172a3801
Yuchen Pei
MDEV-31182 Check for blob too in create_key_parts_for_pseudo_indexes

So that in Item_func_like::get_mm_leaf

the condition

key_part->store_length != key_part->length + maybe_null

is correct
112c317e5b18...
112c317e5b1829779de0afbbdb298625fc64692c
Vladislav Vaintroub
MDEV-37493 I_S.ROUTINES stopped matching db name case-insensitively with lower_case_table_names=2

Since MDEV-14432, get_lookup_field_values() lowercases the WHERE value
only for lower_case_table_names=1, to preserve the letter case of table
names in I_S output. But mysql.proc.db is utf8mb3_bin and always stores
lowercase when lower_case_table_names is non-zero, so with
lower_case_table_names=2 the index lookup in fill_schema_proc() missed.

Fix: lowercase I_S lookup values for any non-zero
lower_case_table_names again. To show db and table names in I_S in
their on-disk letter case (MDEV-14432), resolve exactly-pinned names in
make_db_list() and make_table_name_list() with a new mysys function
my_canonical_case_name(), which returns the canonical name of the last
path component. Unlike before, the true name is now shown even when
the WHERE value uses a different letter case than the on-disk name.
0e57429c00a3...
0e57429c00a3e1a7ed98ca071821e709ee7c3ef6
Sergei Golubchik
cleanup: only include my_compare.h into heap code as needed

to avoid name conflict on `get_key_length`
BuildBot (0.8.9) working for the MariaDB project.
Page built: Tue 07 Jul 2026 08:00:11 (UTC)