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
f2b48e565c09...
f2b48e565c091e0bc913cf8f171ebc5e82e00940
Oleg Smirnov
MDEV-38574 Rename cloning functions of class Item and descendants

Rename cloning methods of class Item and its descendants
in the following way:

  (from)            (to)
do_build_clone  -> deep_copy
  build_clone  -> deep_copy_with_checks

do_get_copy  -> shallow_copy
  get_copy  -> shallow_copy_with_checks

to better reflect their functionality.

Also make Item::deep_copy() and shallow_copy() protected.
Outside users should call deep_copy_with_checks()
and shallow_copy_with_checks().
f18ad925b830...
f18ad925b8309a4934f0a3e29bef19dad9fac882
Oleksandr Byelkin
Wolfssl v5.8.4-stable
f0ffc5d4325f...
f0ffc5d4325f98d31a53dc9712dad07f78162833
Sergey Vojtovich
MDEV-37862 - innodb.gap_locks test failure: 0 lock structs, 0 row locks

Test was affected by incompletely closed preceding connections.

Make test agnostic to concurrent connections by querying
InnoDB status only for connections that it uses.

This is an addition to 3b2169f0d1e, which didn't handle a case when
preceding test has active transaction on disconnect.
e9c643577dd0...
e9c643577dd08d4e5e01cfdf0415fda5737e9f12
Alexey Botchkov
MDEV-35766 ST_PointOnSurface returns NULL with Polygon in some case.

We have to take the ending of a polygon into account.
So the order of checking the scan changed.
e583a7724b3b...
e583a7724b3b7086da119bbdb4f14105637f3ed9
Thirunarayanan Balathandayuthapani
MDEV-37042  innodb_undo_log_truncate=ON leads to out-of-bounds write

During undo tablespace truncation, pages with LSNs older than the
tablespace creation LSN may still exist in the buffer pool and get
submitted to the doublewrite buffer. When mtr_t::commit_shrink() is
invoked shortly after doublewrite batch submission,
this can lead to out-of-bounds write errors.

Fix:
===
buf_dblwr_t::flush_buffered_writes_completed() : skip doublewrite
processing for pages where the page LSN is older
than the tablespace creation LSN. Such pages belong to the old
tablespace before truncation and should not be written through the
doublewrite buffer.
e2c63a7062e3...
e2c63a7062e3acbe44b8f7122c347183b87cbd89
Marko Mäkelä
MDEV-38595: Simplify InnoDB doublewrite buffer creation

buf_dblwr_t::create(): Create the doublewrite buffer in a single
atomic mini-transaction. Do not write any log records for
initializing any doublewrite buffer pages, in order to avoid
recovery failure with innodb_log_archive=ON starting from the
very beginning.

The mtr.commit() in buf_dblwr_t::create() was observed to
comprise 295 mtr_t::m_memo entries: 1 entry for the
fil_system.sys_space and the rest split between page 5 (TRX_SYS)
and page 0 (allocation metadata). We are nowhere near the
sux_lock::RECURSIVE_MAX limit of 65535 per page descriptor.

Reviewed by: Thirunarayanan Balathandayuthapani
Tested by: Saahil Alam
dc67d61d318d...
dc67d61d318d9661e4cbdffb653630c2ed9722b7
Alexey Botchkov
MDEV-15479 Empty string is erroneously allowed as a GEOMETRY column value.

Empty string disallowed.
d75734570303...
d75734570303e02d31faac1b44c46697f36b21c1
Sergei Golubchik
Add test cases for comment handling in audit plugin

The fix was implemented in 635559a.

Previously with the hand-rolled SQL string parsing in the audit plugin, there
were many simple ways to bypass server audit logging by placing comments
strategically in the query string. The fix in 635559a removes the custom SQL
string parser which addresses the issue.

We now add MTRs for validation.
d3aa662d3653...
d3aa662d365370cbc6d4e94666e53b52de2e6206
Alexander Barkov
MDEV-10152 Add support for TYPE .. IS REF CURSOR

Version#2

In progress
cd02709a315c...
cd02709a315c9f08965d6b8fb7e75baaae17a4f4
Oleg Smirnov
MDEV-38574 Rename cloning functions of class Item and descendants

Rename `Item::clone_item()` to `clone_constant()`, and do
the same for any overloads in descendant items.
The function returns non-NULL only for items that represent
constant literals.
cb31d7536beb...
cb31d7536beb62e66048125b56506974a0ae51f0
Sergei Golubchik
MDEV-38604 Assertion `thd->utime_after_query >= thd->utime_after_lock' failed in query_response_time_audit_notify on 2nd execution of SP with query cache

even when PS is served from a query cache, thd->utime_after_query
must be updated.

also, backport the assert from 11.8
c882f9b25a4f...
c882f9b25a4fe27fa38aafe04593807369573c9f
Vladislav Vaintroub
MDEV-37527 Client plugins are underlinked

Provide test case
b6fb760bbb46...
b6fb760bbb46a9e396d18161280595bb0cc8e897
KhaledR57
MDEV-37072: Implement IS JSON predicate

Add support for the SQL standard IS JSON predicate with the syntax:
expr IS [ NOT ] JSON [ { VALUE | ARRAY | OBJECT | SCALAR } ]
[ { WITH | WITHOUT } UNIQUE [ KEYS ] ]

The predicate allows checking if an expression is valid JSON
and optionally constrains the JSON type (VALUE, ARRAY, OBJECT,
SCALAR) and whether object keys are unique.

The implementation includes:
- Basic IS JSON validation
- Support for NOT operator
- Type constraints (VALUE, ARRAY, OBJECT, SCALAR)
- Unique keys constraint (WITH/WITHOUT UNIQUE KEYS)
b505b7421a25...
b505b7421a25f043949c37220c3d6c4635a8b6df
Oleksandr Byelkin
10.6 adjasts
aa2f073a0ebf...
aa2f073a0ebf9fe53ba535cfad5a2d28f29c6548
Alexey Botchkov
MDEV-35766 ST_PointOnSurface returns NULL with Polygon in some case.

We have to take the ending of a polygon into account.
So the order of checking the scan changed.
a8471426f473...
a8471426f473d687c6694d7911e76c1613d05837
Raghunandan Bhat
MDEV-38487: Prevent aggregate function cloning when pushing HAVING into WHERE

Problem:
  When building a pushable condition that can be pushed from HAVING into
  WHERE, the server tries to clone aggregate functions. This is not
  necessary because aggregate functions can not be pushed into WHERE
  anyway.

Fix:
  This fix introduces a check within `Item::build_pushable_cond` to skip
  cloning aggregate functions.

Also fixes assert failure in MDEV-38492, by adding a missing copy method
for `Item_aggregate_ref`.
9f28e7be59de...
9f28e7be59de58b92573351cd69978d7602feb34
Marko Mäkelä
MDEV-23298 fixup: have_perfschema.inc
91824ee28ecd...
91824ee28ecd407af0baa72a7e45ed7ee61deed7
Hemant Dangi
MDL BF-BF conflict on ALTER and INSERT with multi-level foreign key parents

Issue:
On galera write node INSERT statements does not acquire MDL locks on it's all child
tables and thereby wsrep certification keys are also added for limited tables, but
on applier nodes it does acquire MDL locks for all child tables. This can result
into MDL BF-BF conflict on applier node when transactions referring to parent and
child tables are executed concurrently. For example:

Tables with foreign keys: t1<-t2<-t3<-t4
Conflicting transactions: INSERT t1 and DROP TABLE t4

Wsrep certification keys taken on write node:
- for INSERT t1: t1 and t2
- for DROP TABLE t4: t4

On applier node MDL BF-BF conflict happened between two transaction because
MDL locks on t1, t2, t3 and t4 were taken for INSERT t1, which conflicted
with MDL lock on t4 taken by DROP TABLE t4.
The Wsrep certification keys helps in resolving this MDL BF-BF conflict by
prioritizing and scheduling concurrent transactions. But to generate Wsrep
certification keys it needs to open and take MDL locks on all the child tables.

On applier nodes Write_rows event is implicitly a REPLACE, deleting all conflicting
rows which can cause cascading FK actions and locks on foreign key children tables.

Solution:
For Galera applier nodes the Write_rows event is considered pure INSERT
which will never cause cascading FK actions and locks on foreign key children tables.
8ece4d6de941...
8ece4d6de941c5777fe489ab318e1a28d404d74f
Alexey Botchkov
MDEV-35426 Stack smashing in spider_db_mbase::xa_end (opt), ASAN: stack-buffer-overflow in Binary_string::q_append, and Assertion `str.alloced_length() >= str.length() + data_len' failed in spider_string::q_append on SELECT.

The buffer size has to be increased because we store the hexadecimal
representation of the data which takes twice it's length plust the '0x'
starter. Also string representation of the long should be increased.
8906e6a214ab...
8906e6a214ab7d151e44c994cd9149fe3d45d114
Aleksey Midenkov
MDEV-32317 ref_ptrs exhaust on multiple ORDER by func from winfunc

Each ORDER and WHERE slot may generate split, see code like this:

  if ((item->with_sum_func() && item->type() != Item::SUM_FUNC_ITEM) ||
    item->with_window_func())
  item->split_sum_func(thd, ref_ptrs, all_fields, SPLIT_SUM_SELECT);

Such kind of code is done in JOIN::prepare(), setup_order(),
setup_fields(), setup_group() and split_sum_func2() itself.

Since we are at the phase of ref_ptrs allocation, items are not fixed
yet and we cannot calculate precisely how much ref_ptrs is needed. We
can estimate at most how much is needed. In the worst case each window
function generates split on each ORDER BY field, GROUP BY field and
WHERE field, so the counts of these should be multiplied by window
funcs count.

As the split can be done in both setup_without_group() and
JOIN::prepare() simultaneously, the factor of window funcs should be
multiplied by 2.

The similar case may be with inner sumfunc items as of the condition

  item->with_sum_func() && item->type() != Item::SUM_FUNC_ITEM

but factor of these is harder to predict at the stage of unfixed
items.
87b92b17ea9f...
87b92b17ea9fc10ee0d359399ba5a76987cc8ab9
Hemant Dangi
MDL BF-BF conflict on ALTER and INSERT with multi-level foreign key parents

Issue:
On galera write node INSERT statements does not acquire MDL locks on it's all child
tables and thereby wsrep certification keys are also added for limited tables, but
on applier nodes it does acquire MDL locks for all child tables. This can result
into MDL BF-BF conflict on applier node when transactions referring to parent and
child tables are executed concurrently. For example:

Tables with foreign keys: t1<-t2<-t3<-t4
Conflicting transactions: INSERT t1 and DROP TABLE t4

Wsrep certification keys taken on write node:
- for INSERT t1: t1 and t2
- for DROP TABLE t4: t4

On applier node MDL BF-BF conflict happened between two transaction because
MDL locks on t1, t2, t3 and t4 were taken for INSERT t1, which conflicted
with MDL lock on t4 taken by DROP TABLE t4.
The Wsrep certification keys helps in resolving this MDL BF-BF conflict by
prioritizing and scheduling concurrent transactions. But to generate Wsrep
certification keys it needs to open and take MDL locks on all the child tables.

On applier nodes Write_rows event is implicitly a REPLACE, deleting all conflicting
rows which can cause cascading FK actions and locks on foreign key children tables.

Solution:
For Galera applier nodes the Write_rows event is considered pure INSERT
which will never cause cascading FK actions and locks on foreign key children tables.
8575b07f1183...
8575b07f1183c12eb6a81c42050c114de86b07d8
Oleksandr Byelkin
MDEV-35288 Assertion `!is_cond()' failed in virtual longlong Item_bool_func::val_int()

Boolean function now uses val_bool to get string result (val_str())
8437643a36bd...
8437643a36bd5a04868e1b6f7f3a926456000863
Rophy Tsai
MDEV-38431: fix database pointer calculation for long passwords

When a client connects with CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA
capability and a password >= 251 bytes, the server incorrectly
calculates the database name pointer.

For passwords >= 251 bytes, LENENC uses a 3-byte prefix (0xFC + 2 bytes),
but the old code assumed a 1-byte prefix. Fix by using the passwd pointer
which has already been advanced past the length prefix by
safe_net_field_length_ll().

Also fix db pointer calculation for old protocol (!CLIENT_SECURE_CONNECTION)
where the password is null-terminated and needs +1 to skip the terminator.
840ebde8b9a8...
840ebde8b9a8012a216895e182039b6e2fb05944
Oleksandr Byelkin
new CC
7fed01430819...
7fed0143081988e9fbaf01c9e07aa261ec1f06be
Mohammad Tafzeel Shams
MDEV-38140: InnoDB index corruption after UPDATE affecting virtual
columns

Issue:
- Purge thread attempts to purge a secondary index record that is not
  delete-marked.

Root Cause:
- When a secondary index includes a virtual column whose v_pos is
  greater than the number of fields in the clustered index record, the
  virtual column is incorrectly skipped while reading from the undo
  record.
- This leads the purge logic to incorrectly assume it is safe to purge
  the secondary index record.
- The code also confuses the nth virtual column with the nth stored
  column when writing ordering columns at the end of the undo record.

Fix:
- In trx_undo_update_rec_get_update(): Skip a virtual column only
  when v_pos == FIL_NULL, not when v_pos is greater than the number
  of fields.
- In trx_undo_page_report_modify(): Ensure ordering columns are
  written based on the correct stored-column positions, without
  confusing them with virtual-column positions.
7dde0215a042...
7dde0215a042f8aba69691095ad5aa9842cc8be3
Alexey Botchkov
MDEV-36058 ST_CROSSES returns 0 instead of NULL.

Add check for the arguments.
7ae02de3a55e...
7ae02de3a55ed8f0455b253ab17bc978ada050d3
KhaledR57
MDEV-36107 MDEV-36108 Enhance mysqltest language with expression evaluation and variable substitutions

mysqltest had limited scripting capabilities, requiring complex
workarounds for mathematical calculations and string manipulations
in test cases. This commit solves these limitations by adding a new
`$(...)` syntax that enables direct evaluation of mathematical, logical,
and string expressions within test scripts.

Expression Evaluation (MDEV-36107):
- Recursive descent parser supporting arithmetic, logical, comparison,
  and bitwise operators with proper precedence
- Support for integers (decimal, hex, binary), booleans, strings, and
  NULL values
- Variable substitution within expressions
- Integration with existing mysqltest control flow

String Functions (MDEV-36108):
- Base conversion functions supporting bases 2-62
- String manipulation and processing functions
- Regular expression functions
- Conditional and numeric utility functions

The implementation enhances mysqltest's scripting capabilities while
maintaining full backward compatibility.
76fc1861ca4b...
76fc1861ca4b8074357227e6ce4dd627c8b6c67a
gkodinov
MDEV-38642: Missing Null terminator in the definition of mysqldump's --system typelib

There was a missing NULL element terminator for --system's type
library definition.

This was causing a crash in find_type_eol when e.g. an incomplete
value was passed to --system where it keeps iterating until it
finds the NULL as a typelib element.

Fixed by appending a NullS to the definition.
Test case added.
704bc1743c72...
704bc1743c728793f8a64fb279c541a2027aeb4a
Alexey Botchkov
MDEV-36058 ST_CROSSES returns 0 instead of NULL.

Add check for the arguments.
5f6109abe5b4...
5f6109abe5b4abae035f20cba8ef7094c17e2317
Marko Mäkelä
MDEV-38618 Unused variable dict_table_t::fk_max_recusive_level

Ever since mysql/mysql-server@377774689bf6a16af74182753fe950d514c2c6dd
was applied in commit 2e814d4702d71a04388386a9f591d14a35980bfed
the data member dict_table_t::fk_max_recusive_level is never being
read, only initialized as 0. Let us follow the lead of
mysql/mysql-server@b22ac19f104c3b3654601b387c37ee82af180d7a
and remove this useless field.
5b6ad325d2e5...
5b6ad325d2e523b95ab7463f093bd8c0d9529edd
Thirunarayanan Balathandayuthapani
MDEV-38667  Assertion in diagnostics area on DDL stats timeout

Reason:
======
During InnoDB DDL, statistics updation fails due to lock wait
timeout and calls push_warning_printf() to generate warnings
but then returns success, causing the SQL layer
to attempt calling set_ok_status() when the diagnostics area
is already set.

Solution:
=========
By temporarily setting abort_on_warning to false around operations
that prevents warning to error escalation and restore the original
setting after calling HA_EXTRA_END_ALTER_COPY for alter operation.
52a2b721a75c...
52a2b721a75c11eff8f286fb898384c9dece7e33
Tony Chen
Add additional password obfuscation test cases for server audit plugin

- GRANT SELECT ... IDENTIFIED BY
- CHANGE MASTER ... MASTER_PASSWORD
- CREATE SERVER ... PASSWORD
- ALTER SERVER ... PASSWORD

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
496767b310aa...
496767b310aac2f0bcc55261785f69a00eaf289d
Vladislav Vaintroub
pcre2 10.47
470487c1a6ef...
470487c1a6ef29ab5db911739412754acd25e912
Marko Mäkelä
MDEV-21816 Suboptimal implementation of my_convert()

my_convert(): Correctly identify unaligned access by invoking memcpy(),
which will be translated to a single x86 MOV instruction already by
GCC 4.8.5. Also, process the data 64 bits at a time when possible.

The use of memcpy() prevents GCC from emitting a SIMD instruction that
expects aligned memory (MDEV-37148, MDEV-37786, MDEV-38398) and
allows us to enable the fast path across all ISA.

Reviewed by: Alexander Barkov
Reviewed by: Vladislav Vaintroub
30df78fb5ce9...
30df78fb5ce9501b72bcaf54d9d4d600aca17f48
Alexey Botchkov
MDEV-35426 Stack smashing in spider_db_mbase::xa_end (opt), ASAN: stack-buffer-overflow in Binary_string::q_append, and Assertion `str.alloced_length() >= str.length() + data_len' failed in spider_string::q_append on SELECT.

The buffer size has to be increased because we store the hexadecimal
representation of the data which takes twice it's length plust the '0x'
starter. Also string representation of the long should be increased.
2d3c5210bb8d...
2d3c5210bb8dffc4276b8d278278975c57cd5a78
Marko Mäkelä
fixup! 9a4fce9ff36c07f73682893069d167ecb36a5096

Fix ut_ad(!resize_log.is_opened()) in log_t::archive_new_write()
12578d8a69c9...
12578d8a69c9529b080c5e910d53920a8b4f758d
Sergei Golubchik
MDEV-38604 fix SP execution too
0cc287ec8e45...
0cc287ec8e45cc4da773a3fba743e89689e5ab35
Alexey Botchkov
MDEV-35766 ST_PointOnSurface returns NULL with Polygon in some case.

We have to take the ending of a polygon into account.
So the order of checking the scan changed.
09d3ee3643b1...
09d3ee3643b1f3ad74e18bebe26b4d35d5108bc2
Alexey Botchkov
MDEV-35766 ST_PointOnSurface returns NULL with Polygon in some case.

We have to take the ending of a polygon into account.
So the order of checking the scan changed.
05e6c9d42d2f...
05e6c9d42d2f49ada1a0c49a4e0d7fc3ce420e4e
Sergei Golubchik
MDEV-32317 fix the test for --view
BuildBot (0.8.9) working for the MariaDB project.
Page built: Wed 28 Jan 2026 09:13:01 (UTC)