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
f8015f84c819...
f8015f84c819d8eca7c5372b2d29f7a397e16d0a
Sergei Golubchik
cleanup: rename an argument
f2438bce7072...
f2438bce7072945311705ebefd3f6c1401506cac
Oleg Smirnov
MDEV-39349 NO_INDEX hint using QB_NAME doesn't work inside VIEWs
ebc5f5cfa3b8...
ebc5f5cfa3b84ba46a5828eabd0db7025574b13c
Sergei Petrunia
More --disable_replay commands (3).
e21e99afc623...
e21e99afc62324d40dc58671027033330b9013f1
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, delay deallocation of mem_roots created for re-parsing
of SP instructions till the moment the sp_head be destroyed.
dd5cca14e9be...
dd5cca14e9beed72d4ad35e6bb2443f9880315f7
Rophy Tsai
MDEV-38550: add LENENC support for COM_CHANGE_USER

Add support for CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA in COM_CHANGE_USER
packet parsing, allowing passwords >= 251 bytes.

Changes:
- Server: parse_com_change_user_packet() now handles LENENC-encoded
  password length when CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA is set
- Server: fix db pointer calculation for old protocol without
  CLIENT_SECURE_CONNECTION (need +1 to skip null terminator)
- Add regression test for COM_CHANGE_USER with long passwords

Note: This fix requires a corresponding client-side fix in libmariadb's
send_change_user_packet() to send LENENC-encoded passwords.
dd11b48951e1...
dd11b48951e1ced5d5c4e846c8e8825bb1288fd5
Sergei Petrunia
MDEV-39409: Context replay doesn't handle MIN/MAX optimization

Handle it by saving the MIN/MAX rows into Optimizer Context.
Like we do it for const tables.
d86a1f9712bf...
d86a1f9712bfd96cda6d7dafe18a990fc22d6eea
ParadoxV5
MDEV-38600: Annotate the binlogging of recreating MEMORY tables

The data in MEMORY tables is temporary and is lost when the server
restarts. Thus, it is well-intentioned to record TRUNCATE statements
to the binary log when these tables are rediscovered empty. However,
as entries with no explicit user query associated (especially the lack
of SHUTDOWN on crashes), those unaware of this mechanism can find them
unexpected, not to mention their significance downstream in replication.

This commit adds a comment to these automatically generated
TRUNCATE entries to briefly self-describe their source and purpose.
As a part of the generated query, this comment is visible together
with the TRUNCATE itself in SHOW BINLOG EVENTS and `mariadb-binlog`,
while maintaining seamlessness in replication.

There are no other changes in behaviour or storage engine API.

Reviewed-by: Andrei Elkin <[email protected]>
d49e84d5a45d...
d49e84d5a45d38bdd5c6d3f59373d13df7f159f3
ParadoxV5
MDEV-38600: Warn when recreating MEMORY tables on read-only slaves

The data in MEMORY tables is temporary and is lost when the server
restarts. Thus, when these tables are rediscovered empty,
it’s well-intentioned to record TRUNCATE statements to
the binary log, complete with an increment to the `@@gtid_binlog_pos`.
However, those unaware of this mechanism may not expect this increment
and its sign of replication divergence, namely in `@@gtid_strict_mode`.

This commit adds a binary log warning
when such a table is found `implicit_emptied`.

Since general uses of memory tables may already expect this effect,
to avoid unnecessary verbosity, this warning only emits from
`@@read_only` servers with CHANGE MASTER configured. `@@read_only`
indicates that the server should not receive changes; for a slave,
it means it only expects replication to binlog changes with GTID.

Reviewed-by: Brandon Nesterenko <[email protected]>
cee3ff42f690...
cee3ff42f69015aefd89d2dfd1ac3c25f489d295
Sergei Golubchik
MDEV-38550 post-merge fixes

* update to the fixed libmariadb
* update test to match, remove useless INSTALL PLUGIN
* address remaining review comments
cecd77f04a8a...
cecd77f04a8a1b939e858e434d0ecbc32bc115a7
Vladislav Vaintroub
HeidiSQL - prevent stale download by providing expected hash
caac2d7ed340...
caac2d7ed340cbf441ce877d00cea3789accf9e4
ParadoxV5
MDEV-38600: Warn when recreating MEMORY tables on read-only slaves

The data in MEMORY tables is temporary and is lost when the server
restarts. Thus, when these tables are rediscovered empty,
it’s well-intentioned to record TRUNCATE statements to
the binary log, complete with an increment to the `@@gtid_binlog_pos`.
However, those unaware of this mechanism may not expect this increment
and its sign of replication divergence, namely in `@@gtid_strict_mode`.

This commit adds a binary log warning
when such a table is found `implicit_emptied`.

Since general uses of memory tables may already expect this effect,
to avoid unnecessary verbosity, this warning only emits from
`@@read_only` servers with CHANGE MASTER configured. `@@read_only`
indicates that the server should not receive changes; for a slave,
it means it only expects replication to binlog changes with GTID.

Reviewed-by: Brandon Nesterenko <[email protected]>
a7123aed6cf8...
a7123aed6cf8abe9f9deac8a8bbc60627cfe9008
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, delay deallocation of mem_roots created for re-parsing
of SP instructions till the moment the sp_head be destroyed.
9c1c99d414f1...
9c1c99d414f1634b7a03f165ad3072bb3e3c9063
Sergei Golubchik
MDEV-39141 MariaDB crashes in THD::THD() due to misalignment

fix alloc_root() and my_malloc() to return 16-aligned pointers

(type_assoc_array.sp-assoc-array-64bit prints changes in memory_used,
and my_malloc() uses more memory now)
9a8cf00fb47d...
9a8cf00fb47ddd7a31ad62cfd282bf342e786a12
ParadoxV5
Merge branch '10.11' into MDEV-38600
9936b16e12da...
9936b16e12da94f86317d2997c36b6fb7261703e
ParadoxV5
MDEV-38600: Warn when recreating MEMORY tables on read-only slaves

The data in MEMORY tables is temporary and is lost when the server
restarts. Thus, when these tables are rediscovered empty,
it’s well-intentioned to record TRUNCATE statements to
the binary log, complete with an increment to the `@@gtid_binlog_pos`.
However, those unaware of this mechanism may not expect this increment
and its sign of replication divergence, namely in `@@gtid_strict_mode`.

This commit adds a binary log warning
when such a table is found `implicit_emptied`.

Since general uses of memory tables may already expect this effect,
to avoid unnecessary verbosity, this warning only emits from
`@@read_only` servers with CHANGE MASTER configured. `@@read_only`
indicates that the server should not receive changes; for a slave,
it means it only expects replication to binlog changes with GTID.

Reviewed-by: Brandon Nesterenko <[email protected]>
986a260c85e4...
986a260c85e4c4506fd57ed6c3af25ccd6eca63a
Sergei Golubchik
MDEV-38199 Optimizer Error with = SOME on UNIQUE Column Using Decimal/Integer Types

return 1 (non-fatal error) when a decimal or float number
was modified when stored in Field_long (= fractional part was lost).

This tells the optimizer that a number with a non-zero fractional
part cannot be found in an index over an integer field.
9444168a1eae...
9444168a1eaeef4d5e945a92c7dde93c5da7a963
Sergei Petrunia
More --disable_replay for queries where we don't support it.
8e26fd8efde8...
8e26fd8efde8124251ae295729add13443743be6
Sergei Golubchik
zlib 1.3.2
8d3acf4a8f27...
8d3acf4a8f271693398e44f6bb5f258a041d07a6
Sergei Golubchik
MDEV-39318 MTR: fix test failures when running with --ssl

make sure P_S.{global|session}_status and I_S.feedback plugin table
have a column of the same width as I_S.global_status.

Otherwise long status strings (e.g. Ssl_cipher_list) won't fit
and trigger a data truncation warning (an error in the strict mode)
89a23c40fa21...
89a23c40fa218ae1cd2cfaa6b18bbe7405100773
Vladislav Vaintroub
Fix HeidiSQL download URL

HeidiSQL is now released on github, fix the portable ZIP URL to point
to new download location
7e64fdba19db...
7e64fdba19db5a4b4e5d2c2b625f6ded7b8e1d6d
Sergei Golubchik
MDEV-39318 MTR: fix test failures when running with --ssl

make sure P_S.{global|session}_status and I_S.feedback plugin table
have a column of the same width as I_S.global_status.

Otherwise long status strings (e.g. Ssl_cipher_list) won't fit
and trigger a data truncation warning (an error in the strict mode)
7857e9cb4568...
7857e9cb456815b6e6cd99aa124cebc1eea301a3
Sergei Petrunia
[No MDEV#] Fix charset/collation mismatch errors

Make Optimizer Context include
  SET character_set_client=...;
  SET NAMES ... COLLATE ...;
6e5bf40f63cc...
6e5bf40f63cc0a242ac310840088f37679d00583
Sergei Golubchik
cleanup: remove explicit rounding before decimal2longlong

embed rounding into decimal2longlong instead.
this avoid carry propagation loop on rounding.
and allows decimal2longlong detect truncation correctly
60a635b752ac...
60a635b752ace93bc6e8d0c20a3b6e199a1cd37f
Rex Johnston
MENT-2483 Degrading performance with CTE query with spatial index

Enabling derived keys optimization for derived.col = const
Correctly setting records per key in derived key for the optimizer
based on form and contents of derived table.
5dd9a692a004...
5dd9a692a004e589bc3dbb34f33c449f0c47b2e3
Sergei Petrunia
MDEV-39435: Context Replay : Assertion `table_records || !head->file->stats.records' failed

The problem was caused by this scenario:
- The same table can be used multiple times in the query.
- A SELECT may be resolved without ever entering make_join_statistics()
  and set_statistics_for_table(). This will happen if the SELECT is
  handled via opt_sum_query, for example.
- Then, Context Capture code can take this TABLE object and save its
  unitialized statistics into the Optimizer Context.
- When we then attempt to use unitialized statistics in the other
  SELECT that is handled in regular way, we get a failure.

The fix:
- Do not save/restore table->used_stat_records. Do save/restore
  table->file->stats.records and let the SQL layer to copy it to
  used_stat_records (or use EITS data).
5c33e224e42a...
5c33e224e42a0c4f1577e04ebb173a3584c5388b
Oleksandr Byelkin
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
5b665f0069ba...
5b665f0069bada02ccd0be6bcbbc563d343667cd
Brandon Nesterenko
MDEV-38830: SIGSEGV and UBSAN null-pointer-use in TABLE::evaluate_update_default_function on UPDATE

MDEV-38716 (fa36b269f13) fixes were incomplete. It still allowed a
table's default_fields to be left un-restored after an ALTER table
finished its copy_data_between_fields().

This patch actually matches the original conception of MDEV-38716. It
was later changed after finding a test failure in maria.alter, where I
thought the patch broke that test. But actually, maria.alter itself
relies on somewhat broken/inconsistent server behavior.

It is the MDEV-19055 extension of the test which broke. To summarize the
broken part of the test, first, it creates a temporary table t2, adds a
new column of type DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, and adds
a constraint check on that new type:

CREATE TEMPORARY TABLE t2 (a TIME) ENGINE=Aria;
ALTER TABLE t2 ADD b DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP;
ALTER TABLE t2 ADD CHECK (b = 4);

The next part results in inconsistent behavior:

INSERT IGNORE INTO t2 () VALUES (),(),(),();

Prior to this patch, this would create 4 new rows, each with a zeroed
out timestamp for `b`. This is due to a the default_field not resetting
after the ALTER TABLE, thus the DEFAULT CURRENT_TIMESTAMP clause is lost
after the ALTER TABLE ADD CHECK.

With this patch, because the default_field is restored after the ALTER,
there is no affect of the INSERT IGNORE INTO t2. I.e., t2 is empty after
this insert.

This change in results further changes how an ALTER TABLE behaves later
in the test:

SET SQL_MODE= 'STRICT_ALL_TABLES';
SELECT count(a),sum(a) FROM t2;
--error ER_TRUNCATED_WRONG_VALUE
ALTER TABLE t2 CHANGE IF EXISTS d c INT;

Without this patch, there are rows in t2, and so this ALTER TABLE
results in an error. With this patch, t2 is empty, and therefore there
is no data that was truncated to warn about. It is generally bad test
practice to have a table with no rows, as it has historically masked
other bugs. So we add back a couple rows into the table to ensure it
hits additional logic. However, because the bug has been fixed, invalid
rows are not able to be inserted into the table and thereby the
ER_TRUNCATED_WRONG_VALUE error is still not thrown. So that error is
removed.

Reviewed-by: Monty <[email protected]>
Signed-off-by: Brandon Nesterenko <[email protected]>
59e591e2ff42...
59e591e2ff4258a5cc7522f87705d155b8a74472
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, delay deallocation of mem_roots created for re-parsing
of SP instructions till the moment the sp_head be destroyed.
56a7222f75e7...
56a7222f75e7a8846c9903c9b3defc4e4a595c7d
Sergei Golubchik
MDEV-39141 MariaDB crashes in THD::THD() due to misalignment

fix my_malloc() to return 16-aligned pointers

(type_assoc_array.sp-assoc-array-64bit prints changes in memory_used,
and my_malloc() uses more memory now)
54e3c5964dd3...
54e3c5964dd3c99a8b74b04b1b10321f18dd2e66
Rex Johnston
MENT-2483 Degrading performance with CTE query with spatial index

Enabling derived keys optimization for derived.col = const
Correctly setting records per key in derived key for the optimizer
based on form and contents of derived table.
546786688f54...
546786688f54cd4c654f048280eb7bd9aba8c9ae
Sergei Petrunia
MDEV-39447: Context Replay: "Field doesn't have default value" error

Instead of REPLACE INTO, use
SET STATEMENT sql_mode={remove STRICT_...TABLES} REPLACE INTO.
41887368d91d...
41887368d91db1f7fbd07f2c301dfb26a6d34af6
Sergei Petrunia
MDEV-39368: Make --replay-server-manual also provide a gdb include file.
375809cd5dbf...
375809cd5dbf9a109df502d5f476eb2d458d0447
Sergei Golubchik
MDEV-39112 fix RPAD too
3730b92be0d2...
3730b92be0d2f70c9b612bbcc3be18e5dfb22c10
Sergei Golubchik
zlib 1.3.2
1f95e78ba0b6...
1f95e78ba0b6b34ee463aa27218dfd25674ec934
Sergei Golubchik
Un-deprecate keep_files_on_create

originally (MDEV-23570) the idea was to make it TRUE and deprecate.
It cannot be deprecated when it's FALSE, but TRUE breaks
mariabackup.aria_backup where a table is altered from Aria to InnoDB
during a backup, so both t.MAD/t.MAI and t.ibd gets into a backup.
This is MDEV-38866, when it's fixed, keep_files_on_create can be
enabled by default and deprecated at last.
1f168de4e098...
1f168de4e09838ffe14da061142ed387541aa25d
Sergei Golubchik
CONC-819 mysql_real_escape_string incorrectly handles big5

use (uchar) cast for big5, just like for any other charset.

also, fix gbk unit test to use the full test string length
  • 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
16a25d1d8c57...
16a25d1d8c571de0a5b73218a6fac3a75dcbb749
ParadoxV5
MDEV-38600: Warn when recreating MEMORY tables on read-only slaves

The data in MEMORY tables is temporary and is lost when the server
restarts. Thus, when these tables are rediscovered empty,
it’s well-intentioned to record TRUNCATE statements to
the binary log, complete with an increment to the `@@gtid_binlog_pos`.
However, those unaware of this mechanism may not expect this increment
and its sign of replication divergence, namely in `@@gtid_strict_mode`.

This commit adds a binary log warning
when such a table is found `implicit_emptied`.

Since general uses of memory tables may already expect this effect,
to avoid unnecessary verbosity, this warning only emits from
`@@read_only` servers with CHANGE MASTER configured. `@@read_only`
indicates that the server should not receive changes; for a slave,
it means it only expects replication to binlog changes with GTID.

Reviewed-by: Brandon Nesterenko <[email protected]>
12fd1ca4e4ca...
12fd1ca4e4cadd64b28dcc80e8698f08117c3002
Rophy Tsai
MDEV-38550 add LENENC support for COM_CHANGE_USER

When the server advertises CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA,
use mysql_net_store_length() for auth data in send_change_user_packet()
instead of a single-byte length capped at 255. This allows auth plugins
that produce >255 bytes of auth data (e.g. cleartext with long passwords)
to work with COM_CHANGE_USER.
  • 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
0d2f2945f67d...
0d2f2945f67df19473928c867febef67fe06e739
Sergei Golubchik
MDEV-36345 Memleak on shutdown in acl_load_mutex test

disable main.show_all_plugins if ASAN and RocksDB.

RocksDB has STB_GNU_UNIQUE symbols, so won't be unloaded on dlclose().
Presumably some destructors aren't called, and LSAN doesn't like it.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Sun 26 Apr 2026 20:57:35 (UTC)