Console View

Categories: connectors experimental galera main

Legend:

Passed

Failed

Warnings

Failed Again

Running

Exception

Offline

No data

connectors

experimental

galera

main

ff876b39b32a...

ff876b39b32aba97041d7b449e5539060705125f

Alexey Yurchenko

alexey.yurchenko@mariadb.com

MDEV-38147 add missing result file for MDEV-38147_gtid_off test

f969bd80c7b7...

f969bd80c7b7efec2a48fefcf9f9ff108c92c841

Thirunarayanan Balathandayuthapani

thiru@mariadb.com

MDEV-40621 InnoDB: Failing assertion: doc_id == src_node->last_doc_id

AuxRecordReader::default_word_processor(): InnoDB fails to consider
the ilist data can be stored externally while decoding the auxiliary
table record.

f51edd8933e3...

f51edd8933e3b7c9e796864c7e6c61e25828b4b4

Fariha Shaikh

farihais@amazon.com

MDEV-39153 Fix sporadic main.change_master_default mismatch

The test used "restart_abort:" in the expect file, which MTR never
recognized. It fell through to the else branch, deleted restart_opts,
and started the server with defaults (heartbeat_period=60 instead of 0).

Replace restart_abort with direct --exec $MYSQLD calls.

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. I am contributing on behalf of my employer Amazon Web
Services, Inc.

f2ce815a5e26...

f2ce815a5e266cb6f37c4e6ccbf8fc79f9750ac1

bsrikanth-mariadb

srikanth.bondalapati@mariadb.com

MDEV-39226: Add multi-table update, delete feature

f200933ceb24...

f200933ceb24ddfdec59f7d200b69d2dd5a4f951

Dave Gosselin

dave.gosselin@mariadb.com

MDEV-39441: Add dbug_print() helpers for join-related types

Introduces new dbug_print() functions for the following types:
dbug_print(NESTED_JOIN)
dbug_print(JOIN)
dbug_print(TABLE_LIST)
dbug_print(JOIN_TAB)
dbug_print(List<Item>)

Typically pointers to instances of the given types are passed.
The dbug_print(List<Item>) is intended to show result row before
sending to client (e.g., invoke in debugger while tracing end_send)
but may work in other contexts.

These functions produce nicely formatted output, please use them
in conjunction with the formatted printfs available in GDB or LLDB:
(gdb) printf "%s", dbug_print(join_tab)
(lldb) p printf("%s", dbug_print(table))

Example output from dbug_print(JOIN) in LLDB. The last line with
value 1302 is the number of characters produced by the printf
command.

(lldb) p printf("%s",dbug_print(join))
JOIN [0x15801bfe8] table_count=3 const_tables=0
join_list 0x158018340 [1 element(s)]:
--- #0 ---
[0x15801af10] "(nest_last_join)" join=INNER (outer_join=0) nested_join=0x15801b618 (elements=2)
NESTED_JOIN [0x15801b618]
used_tables: 0x0
not_null_tables: 0x0
n_tables: 0
counter: 0
nest_type: 1 (JOIN_OP_NEST)
nj_map: 0x0
join_list:
join_list 0x15801b618 [2 element(s)]:
--- #0 ---
[0x15801a308] "t3" join=LEFT (outer_join=1) map=0x4
ON: `test`.`t2`.`a` = `test`.`t3`.`a`
--- #1 ---
[0x158019b30] "(nest_last_join)" join=INNER (outer_join=0) nested_join=0x15801a238 (elements=2)
NESTED_JOIN [0x15801a238]
used_tables: 0x0
not_null_tables: 0x0
n_tables: 0
counter: 0
nest_type: 0
nj_map: 0x0
join_list:
join_list 0x15801a238 [2 element(s)]:
--- #0 ---
[0x1580187c0] "t1" join=RIGHT (outer_join=2) map=0x1
ON: `test`.`t1`.`a` = `test`.`t2`.`a`
--- #1 ---
[0x158018f08] "t2" join=INNER (outer_join=0) map=0x2
(int) 1302

e23eb0b8a9e0...

e23eb0b8a9e04e31c7be7d5bdd17569211da653e

Oleksandr Byelkin

sanja@mariadb.com

Merge fix

da0beac410cc...

da0beac410cc761be4ee52b90fded6c7fa2f8947

Ahmad

ahmedshapan913@gmail.com

MDEV-39858: Reloading COSINE metric index from disk degrades search recall due to abs2 quantization noise

When a vector is created in-memory using FVector::create() during normal inserts, its squared magnitude (abs2) under the COSINE metric is hardcoded to 0.5f.

However, when the index is reloaded from disk (after a server restart, FLUSH TABLES, or ALTER TABLE), the index uses FVectorNode::load_from_record(). This method reads the stored scale and quantized int16 coordinates from the database record, and runs postprocess(). Inside postprocess(), abs2 is dynamically recomputed using floating-point math:
abs2 = subabs2 + scale * scale * dot_product(d, d, vec_len) / 2;

Because the coordinates stored on disk are quantized int16 values, this recalculation introduces rounding noise.

This affects high dimensions datasets, and it is increasing as M increases.

Added hardcoded abs2=0.5 to FVectorNode::load_from_record and removed postprocess()

d26f9ab217a7...

d26f9ab217a7fcf9d4eccc62c01020ff275ff42e

Sergei Golubchik

serg@mariadb.org

MDEV-40229 I_S.VECTOR_INDEXES: Unclear or inconsistent semantics of INDEX_SIZE

11.8 fix for I_S.TABLES.INDEX_LENGTH column

Take into account both data_file_length and index_file_length,
they both take space and both belong to the vercor index.

d00a4191ae7c...

d00a4191ae7c58768a530eb4638bedc7a4d18bc0

Lawrin Novitsky

lawrin.novitsky@mariadb.com

ODBC-502 Driver can read and send to server memore past query end

This happened if UTF16 character with UnixODBC(i.e. Linux and not
Window) would have lower byte as the high byte in a surrogate pair
leading unit. One of helper functions erroneously took such character as
leading unit of a surrogate pair, and vise versa - would not recognize
real leading unit as such. That could lead to calculated byte length
would be longer, than the real one, it will be used for query text
transcoding to connection charset and thus memory past he end of query
read and sent to the server.
SQLNativeSqlW had the problem caused be similar reasons, but it did not
need length in char calculation, but in SQLWCHAR units.
The tast has been added and SQLNativeSqlW test thas been extended.

c567deb95ad7...

c567deb95ad7469875b2e2f442bad4f492588db7

Oleksandr Byelkin

sanja@mariadb.com

Merge branch '11.4' into bb-11.4-release

c4c860ec549c...

c4c860ec549cb65d7d112121ff8524507e8fc353

Oleksandr Byelkin

sanja@mariadb.com

Merge branch '11.8' into bb-11.8-release

c28b4efdd4be...

c28b4efdd4be4e46be3421cd0190d629cb862e6d

Sergei Golubchik

serg@mariadb.org

cleanup: mariadb-dump

remove dead code, handling of MariaDB/MySQL servers that didn't
have SQL_QUOTE_SHOW_CREATE.

SQL_QUOTE_SHOW_CREATE was added in 2000
(commit 5762523b788, MySQL 3.23.25-beta)

bd127faa659b...

bd127faa659bffb91cd659c5f739af30c8aba690

Fariha Shaikh

farihais@amazon.com

MDEV-33660 Add note when setting AUTO_INCREMENT lower than next value

Currently, ALTER TABLE ... AUTO_INCREMENT = N silently fails when using
values lower than the next AUTO_INCREMENT value in the column.

Add a note when attempting to set AUTO_INCREMENT to a lower value than
the next AUTO_INCREMENT value, and maintain the higher value.

Update existing test suites and add a new test to the maria suite for
the newly added note.

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. I am contributing on behalf of my employer Amazon Web
Services, Inc.

bc8ef06ee960...

bc8ef06ee96002de33e35bbd43f077801290b692

Dave Gosselin

dave.gosselin@mariadb.com

bc3939b84b71...

bc3939b84b71baa816cf9011fd04f7bbbf43dffd

Daniel Black

daniel@mariadb.org

MDEV-17846 Wrong result with grouping select (fix)

Prevent unused variable 'ref_type' warnings on non-debug builds.

bb0ac437015d...

bb0ac437015dec04fbee226745a8eb2bb4825917

Yuchen Pei

ycp@mariadb.com

MDEV-40486 Length check for vector fields in CREATE TABLE ... SELECT

The changes of MDEV-39558 2b6529426a7e7c65d286e093d84138be9dcc34a3
added length check assertion in Field_varstring constructors, and
length check in type inference for SELECT set operations, to emit
errors before reaching the assertions.

That change caused an error to turn into an assertion failure in a
separate path, when the length limit violation is not detected before
tripping the assertion. So in this patch we fix it by adding an
earlier length check in that path.

The reason that we place this check inside
Item_func_vec_fromtext::fix_length_and_dec rather than say
`create_field_for_create_select is for consistency:

If

create table t1 as select
vec_fromtext(concat('[',group_concat(1),']')) as c1 from seq_1_to_64;

fails due to length limit violation, then so should

create table t1 (v vector(64) not null);
insert into t1 select vec_fromtext(concat('[',group_concat(1),']'))
from seq_1_to_64;

Also use max_char_length() instead of max_length. This is a more
accurate length of characters. And add handling of empty string edge
case. Added testcases accordingly.

The change that uses max_char_length() causes side effects where
creating a table using a VEC_FROMTEXT(CHAR(1)) would result in a
0-dimensional vector field. This is accurate but 0-dim vector table
fields should not be allowed. So we make cases like this result in
a one-dimensional field.

Also fixed the underflow in (args[0]->max_length - 1) * 2 when the
arg's max length is 0. Previously this underflow would cause

create table t1 select vec_fromtext(NULL)

to fail with ER_TOO_BIG_FIELDLENGTH. Now it will be a VECTOR(1) field

b931524cee5d...

b931524cee5d5810335dc61bb914e81a92f3f2c0

bsrikanth-mariadb

srikanth.bondalapati@mariadb.com

MDEV-39226: Add multi-table update, delete feature

a1b3f980dddb...

a1b3f980dddb03f3426f5020f6db5755630d56fb

Sergei Golubchik

serg@mariadb.org

MDEV-33463 Add an option to truncate excessively long queries in the slow log

9f27056cbae2...

9f27056cbae2f3c8e4db2dee37dd5fe1ca8c71a8

Oleksandr Byelkin

sanja@mariadb.com

Merge branch 'bb-10.11-release' into bb-11.4-release

91156c3de587...

91156c3de58762196605150ab3f756fe952592d1

Alexander Barkov

bar@mariadb.com

MDEV-40639 Open SYS_REFCURSOR crash, if many cursors inside a function

Problem:

If:
- A routine A() opened a SYS_REFCURSOR with a function B() in the SELECT list
- The function B() also opened some SYS_REFCURSORs

Then reallocation of the cursor array THD::m_statement_cursors could happen
during the execution of B(), so all sp_cursor_array_element pointers inside
sp_instr_copen_by_ref::exec_core() of routine A() became invalid.

Fix:

Chaging the data type of sp_cursor_array:
- from Dynamic_array<sp_cursor_array_element>
- to Dynamic_array<sp_cursor_array_element*>

So now only reallocations of the array of cursor pointers happen,
while sp_cursor_array_element instances always stay on their originally
allocated memory positions.

Note:
sp_cursor_array_element instances are allocated using the standart C++ "new"
and deleted using the standard C++ "delete". Using a MEM_ROOT does not
seem to be relevant here.

7a9aef7627c6...

7a9aef7627c61b9c4c0b7be9ea55f1dd76e0db4d

Sergei Golubchik

serg@mariadb.org

MDEV-40406 hide #mysql50# under old mode

6c7d3fd59569...

6c7d3fd595691cec676067972a10f97603da0716

Rex Johnston

rex.johnston@mariadb.com

MDEV-40012 Parallel Query: execute the join in the worker threads

Each parallel worker now runs the join and the WHERE over its own chunk of the
driving table and ships the base-table columns of every row that qualified. The
manager copies those columns back into the fields they came from in its own
table instances, so that after a row is drained its records hold what a serial
scan would have left there, and then evaluates the select list against them and
sends the row. This replaces the model where the workers shipped raw source
records and the manager ran the join.

The transport carries columns rather than projected values because anything the
manager does with a row beyond sending it reads a record, and not all of those
reads go through Items that could be re-pointed: create_tmp_table() builds
Copy_field pairs holding raw Field pointers into the base tables.

make_join_readinfo()'s gate, can_run_query_in_workers(), chooses the worker-side
path for an inner select-project[-join] over a parallel-scannable driving table:
no tmp table, no LIMIT/SQL_CALC_FOUND_ROWS/procedure/aggregate, no outer join,
no semijoin strategy the worker's plain nested loop cannot honour, and every
non-driving table reached by eq_ref, ref or full scan. Every expression it hands
a worker has to deep-copy into something that shares no node with the original
and reads no table outside the join, or the copy would carry the manager's own
items onto a worker's tables. do_select() then runs run_worker_side_join();
anything ineligible runs serially.

Each worker opens a private copy of every non-const table, deep-clones and
field-rebinds the conditions and the shipped column list, rebuilds each ref,
scans its chunk, runs its own inner nested loop and ships the columns it read
for each full match. It runs under the session's query id, so an item holding a
value for the statement recomputes it rather than handing out the one it was
cloned with.

sql_parallel_execution.cc holds all of the above; sql_parallel_workers.cc keeps
the worker threads, the batch channel and their lifetime.

Tests: parallel_query_worker_side, parallel_query_join and parallel_query_clone
compare a parallel result set against a serial one; parallel_query and
parallel_query_oom moved to a plain SELECT and were re-recorded.
.claude/commits/MDEV-40012.md records what came from the 13.0 branch verbatim,
what was adapted to this tree, and what is new here.

This commit was prepared with Claude Code: it ported the work from the 13.0
branch onto this tree's refactored structures and renamed scan API, found and
fixed the two holes this tree's deeper Item copying opens -- an expression
reaching a table the worker does not have, and a statement-lifetime item cached
against query id 0 -- split the file, and ran the suites.

53b1cc014932...

53b1cc0149328c7d3857d9d0d6efbbbc779ac2c2

Alexander Barkov

bar@mariadb.com

MDEV-28498 Incorrect information in file: './test/t0.frm' on CREATE TABLE

Applying HEX encoding write writting an ENUM/SET TYPELIB to FRM
if the TYPELIB has 0x00 bytes in the value.

This HEX encoding was earlier used only to write UCS2/UTF16/UTF32 TYPELIBs.

A new flag FIELDFLAG_FRM_HEX_ENCODED_TYPELIB was added to indicate
that the TYPELIB is hex encoded. It's used only inside FRM.
Note, it's mangled with FIELDFLAG_TREAT_BIT_AS_CHAR.
This should not be harmful:
- BIT and ENUM/SET columns are handled by two separate code branches
when opening an FRM
- The flag is unset immediately after decoding TYPELIB, so the rest
of the code does not se an unexpected flag combination.

3660c85bdbec...

3660c85bdbece1405e4fcdb5603a652e4a61f430

Rex Johnston

rex.johnston@mariadb.com

MDEV-38801 Item_sum & Item_cache implement deep_copy()

{Item_cache,Item_cache_row,Item_sum}::deep_copy() currently call
shallow_copy_with_checks(). This causes issues when a proper
independent copy is required, e.g. in add_key_part called on a key
with a value containing an item inherited from Item_cache.
We implement a proper deep copy that shares no nodes with the source,
and add a check to ensure this.

354565cb9dcf...

354565cb9dcf1b7fb8904fcf859d79135921e8d3

Lawrin Novitsky

lawrin.novitsky@mariadb.com

3055c336b118...

3055c336b1183b09a081e062c9d792d508c4fbc7

Rex Johnston

rex.johnston@mariadb.com

2fa3b0f0c4b6...

2fa3b0f0c4b66f302b70e213fdf83f866adff7ec

Daniel Black

daniel@mariadb.org

MDEV-37224 Remove UBSAN limitation from MTR tests

Having a not_ubsan.inc as a test case exclusion mechanism is
allowing developers to ignore UBSAN issues. As undefined behaviour
detected at runtime or compile time isn't acceptable in the
code base, remove the exclusion.

The lotofstack test, the only user of not_ubsan.inc, has this
exclusion because the stack size under UBSAN lacks predictability.

Adjust its exclusion because of this criteria, and not its UBSAN
status.

Reviewer: Jimmy Hu <[email protected]>

1f11614ce75c...

1f11614ce75c6a49db3ef9bddb951bb0e1c8671f

Oleksandr Byelkin

sanja@mariadb.com

Merge branch 'bb-11.4-release' into bb-11.8-release

12ceb4d6aac1...

12ceb4d6aac1c287f4e2bf8d0412795f4e539020

Daniel Black

daniel@mariadb.org

MDEV-34482 main.events_processlist test fix

As the test result is dependent of SHOW PROCESSLIST output,
adjust the wait condition to ensure the state is in sleeping
rather than "init" or another state.

128c7b41d0c0...

128c7b41d0c0497e84aee806e59c3133c59dc17c

Oleksandr Byelkin

sanja@mariadb.com

Merge branch '10.11' into bb-10.11-release

0ee34e07bdc1...

0ee34e07bdc10abf32a535d7234c6f5e0bb9ed55

Alexander Barkov

bar@mariadb.com

MDEV-39587 Package-wide TYPE for variable declarations

SET sql_mode=ORACLE;
DELIMITER $$
CREATE OR REPLACE PACKAGE pkg AS
-- Declare a package public data type
TYPE varchar_array IS TABLE OF VARCHAR(2000) INDEX BY INTEGER;
END;
$$
DELIMITER ;
DELIMITER $$

CREATE OR REPLACE PROCEDURE p1 AS
v pkg.varchar_array; -- Use the package public data type
BEGIN
v(0):='test';
SELECT v(0);
END;
$$
DELIMITER ;

Note, the change is done only for sql_mode=ORACLE, because the TYPE
declaration is not available for the default mode.

Where package-wide types are available
--------------------------------------
- Variabe list type:
DECLARE var pkg1.type1;

- RETURN type for a package routine:
CREATE FUNCTION .. RETURN pkg1.type1 ...

- Parameter type for a package routine:
PROCEDURE p1(param1 pkg1.type1);

- Assoc array element type:
TYPE assoc1_t IS TABLE OF pkg1.type1 ...

- REF CURSOR RETURN type:
TYPE cur1_t IS REF CURSOR RETURN pkg1.type1;

Change details
--------------

- Adding a member Lex_length_and_dec_st::m_foreign_module_type
It's set to true when the data type was initialized from a TYPE
in foreign routine (e.g. in PACKAGE spec).
It's needed to prevent use of qualified identifiers in public contexts,
i.e. in schema public routine parameter types and schema publuc function
RETURN types.
Adding a helper method sp_head::check_applicability() which prevents
use of qualified types in public context.

- Adding a helper method sp_head::raise_unknown_data_type().

- Adding methods LEX::set_field_type_typedef_package_spec() for
2-step and 3-step qualified indentifiers.
It's used in field_type_all_with_typedefs which covers cases:
- Variabe list type : DECLARE var pkg1.type1;
- RETURN type : CREATE FUNCTION .. RETURN pkg1.type1 ...
- Parameter type : PROCEDURE p1(param1 pkg1.type1);
- Assoc array element type : TYPE assoc1_t IS TABLE OF pkg1.type1 ...

- Adding a method LEX::declare_type_ref_cursor_return_typedef().
It handles cases when a new TYPE REF CURSOR RETURN is declared,
for both for qualified RETURN types and non-qualified RETURN types:
- TYPE cur0_t IS REF CURSOR RETURN rec1_t;
- TYPE cur0_t IS REF CURSOR RETURN pkg1.rec1_t;
- TYPE cur0_t IS REF CURSOR RETURN db1.pkg1.rec1_t;

The code was moved from LEX::declare_type_ref_cursor() into
LEX::declare_type_ref_cursor_return_typedef() and extended
to cover qualified RETURN types.

- Adding a method Sql_path::find_package_spec_type().
It iterates through all schemas specified in @@path and searches
for the given type in the given package.

- Adding a helper method sp_pcontext::type_defs_add_ref_cursor()
to reuse the code.

- Adding a new method sp_package::get_typedef() to search
for TYPE definitions in PACKAGE specifications.

- Adding a new method sp_head::get_typedef_package_spec()
to search for TYPE definitions used by a PROCEDURE or FUNCTION.

- Adding a helper method
Sp_handler::sp_cache_routine_reentrant_suppress_errors
Adding a method Sp_handler::find_package_spec().

0e4665391152...

0e466539115292ec02ce0731d949902d1db23291

Sergei Golubchik

serg@mariadb.org

cleanup: remove buggy str2int, replace with a template

remove one str->int implementation (we still have 10+ more),
replace with a convenience template that calls my_strntoll_8bit()

0cb69e4c1c6d...

0cb69e4c1c6d9efdb1b163acf5c757346f5b783b

Thirunarayanan Balathandayuthapani

thiru@mariadb.com

0777bf0ee36f...

0777bf0ee36f3403a2975fb5a93970521b7cac4a

Kristian Nielsen

knielsen@knielsen-hq.org

MDEV-40729: Add functionality to verify if a transaction is committed or not after failure

Basic proof-of-concept patch, only implements the basics to put xact_id into
the binlog file and search for it with xact_status().

A test case rpl.rpl_client_xact_id demonstrates the functionality.

Some limitations/considerations from this patch:

There is no support for MARIADB_XACT_IN_PROGRESS (do we want/need such
functionality?).

Based on 10.11, however pushing to stable 10.11 will be controversial as it
changes GTID event format.

Since 10.11 has no GTID indexes, linear scan of at least one entire binlog
file will be required. An in-memory cache may be needed to handle client
reconnect-storm after a crash or network outage that caused many ongoing
commits to fail.

When starting gtid is not specified for xact_status(), it is not possible to
distinguish between MARIADB_XACT_ABORTED or MARIADB_XACT_UNKNOWN. In this
case, we return MARIADB_XACT_ABORTED.

Knowing where to start scanning binlogs is important, for performance (to
avoid scanning _entire_ binlog history), and to distinguish
MARIADB_XACT_ABORTED from MARIADB_XACT_UNKNOWN. It is somewhat tricky
though:

- A GTID position is multi-dimensional. The starting GTID _must_ be with
the same domain_id as the transaction being searched for, otherwise
searching on a slave may start too late in the slave's binlog and wrongly
return MARIADB_XACT_ABORTED for a committed transaction.

- The client will need to obtain a starting GTID for the very first
transaction done on the connection. One possible way could be to
SELECT @@GLOBAL.gtid_binlog_pos and pick out the one with the domain_id
which will be used for subsequent transactions.

Signed-off-by: Kristian Nielsen <[email protected]>

046c9182bc1a...

046c9182bc1a77dcfb531c85220f31a339ff907a

Sergei Golubchik

serg@mariadb.org

remove checks for strto[u][l]l family

040824c33ac3...

040824c33ac363f250ae1c24cda7eadabd4cc2d6

Fariha Shaikh

farihais@amazon.com

MDEV-39459 Fix bad sync pattern for chain replication MTR tests

In chain replication (1->2->3), syncing only server_3 after
save_master_gtid on server_1 does not guarantee server_2 has committed,
because server_2's binlog dump thread can send events to server_3 before
commit_ordered() completes on server_2.

Fix affected rpl tests by syncing server_2 before server_3, and update
result files accordingly.

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. I am contributing on behalf of my employer Amazon Web
Services, Inc.