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
fd46e1838d8b...
fd46e1838d8b7b0a8d9057cf430b715ef5be11d7
Jan Lindström
Merge remote-tracking branch 'upstream/4.x' into galera-26.4.28
f7bb81faca28...
f7bb81faca286f74474925be6bd99a16675d8867
Sergei Golubchik
MDEV-40445 TLS 1.3 early data
f6a3a9893ff3...
f6a3a9893ff38cfefeb9deebd7d3735e29092002
Sergei Petrunia
Introduce pwt_manager::notify_fatal_error(), move code there.

Also make members private and TODO comments.
e199a6b5a1d7...
e199a6b5a1d71bc750ef0dc16238aeca6bac4310
Marko Mäkelä
MDEV-40728 Recovery wrongly fails if FILE_CREATE is followed by FILE_RENAME

deferred_spaces.deferred_dblwr(): Skip newly created tablespaces
to avoid a bogus invocation of fil_space_free().

fil_name_process(): Simplify the logic. If no matching tablespace is
found but file_name_t::create_lsn had been set in response to parsing
a FILE_CREATE record, try to apply FILE_RENAME to deferred_spaces.

log_parse_file(): Parse each FILE_ record only once. In multi-batch
recovery, there may be redundant calls that would break the logic of
fil_name_process().
c9ccb3c2ac33...
c9ccb3c2ac33be169fbd59d428456900e0d35b00
Sergei Golubchik
MDEV-12320 change initial authentication plugin in the server

instead of unconditionally starting the authentication from
the mysql_native_password, start it from the plugin that will most
likely avoid "change plugin" packet (and thus a round-trip). Maintain
counters of what plugins were used to authentify users so far, use
the plugin with the largest count for new connections.

FLUSH PRIVILEGES resets the stats.
bfcae13eedcb...
bfcae13eedcbb2271f5a64fdcd8b7c9b9be2c9b4
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.
in a bare function call.

Both DEFAULT 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 at 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.

- Only bare function calls are supported for now. Using a function in
  an expression does not make it PS-safe yet yet:
    SET v= f1()+0;
be4f2b74621f...
be4f2b74621f773e35303aea10e96f32e6733b02
Sergei Golubchik
MDEV-40445 TLS session resumption

in fact it was already on in the server, so this only
enables statistics to see it in SHOW STATUS, adds tests,
and updates C/C to match.

Assisted-By: Claude:claude-5-opus
bb8c5ee39c3d...
bb8c5ee39c3d17a95adbb75a7698254660e3b8e3
Otto Kekäläinen
Make Galera compatible with OpenSSL 4.0

OpenSSL 4.0 made several X509 getters const-correct, now return const
pointers. However, the corresponding mutating functions still require
non-const arguments.

Add const_cast where needed to satisfy the type system on OpenSSL 4.0
while remaining compatible with OpenSSL 1.x and 3.x, where the getters
return mutable pointers.

Grepping for OpenSSL API calls, no other files in the repository seem to
use these APIs, so the change is complete and fully backwards-compatible.

Related: https://jira.mariadb.org/browse/MDEV-40655
b96331bc7d3c...
b96331bc7d3c7480c02dfc8a3eef90d3dadc29c1
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.
b2c4e675049e...
b2c4e675049e23ce8c7346985f40840fcd4e583f
Marko Mäkelä
MDEV-40728 Recovery wrongly fails if FILE_CREATE is followed by FILE_RENAME

deferred_spaces.deferred_dblwr(): Skip newly created tablespaces
to avoid a bogus invocation of fil_space_free().

fil_name_process(): Simplify the logic. If no matching tablespace is
found but file_name_t::create_lsn had been set in response to parsing
a FILE_CREATE record, try to apply FILE_RENAME to deferred_spaces.

log_parse_file(): Parse each FILE_ record only once. In multi-batch
recovery, there may be redundant calls that would break the logic of
fil_name_process().

fil_delete_apply(): Wrappers for fil_space_free(). When recovering
a log in innodb_log_archive=ON format, we must apply FILE_DELETE
records in order to avoid a future clash with FILE_CREATE or FILE_RENAME.
9b7c9b922651...
9b7c9b9226513b73d66326d3d61ca5b6bcc74e21
Sergei Golubchik
cleanup: remove pre-locking of old_password_plugin

nobody should be using it, so this "optimization" actually isn't.
95054b977737...
95054b977737cc62b30b9c9e355b0aa388280e90
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.
908e21b6e4a9...
908e21b6e4a980c3965c6bfc3c5a501e32b7438c
Yuchen Pei
MDEV-40168 wip

works:

create table t1 (c int, j json, key idx ((CAST(j->'$.tags' AS CHAR(6) ARRAY))));
SHOW CREATE TABLE t1;
Table Create Table
t1 CREATE TABLE `t1` (
  `c` int(11) DEFAULT NULL,
  `j` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL CHECK (json_valid(`j`)),
  `DB_MVI_1` text CHARACTER SET latin1 COLLATE latin1_bin GENERATED ALWAYS AS (json_extract(`j`,'$.tags')) STORED,
  FULLTEXT KEY `idx` (`DB_MVI_1`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci
DROP TABLE t1;
8a13e65d5d0e...
8a13e65d5d0e8a79cb862dd679308d83aa0eb14b
Sergei Golubchik
cleanup: redo thd_create_random_password() from thd_rnd service.

* it was only used in sql_acl.cc to generate scramble, not used
  by plugins
* rename to thd_get_session_nonce() that explicitly generates
  session nonce (or "scramble")
* the function returns the existing nonce if it was already
  generated, or generates and saves it in THD, it always does the full
  nonce length, only uses characters in a given range, zero-terminates.
* incompatible change, service version is bumped to 2.0
* parsec also uses thd_get_session_nonce() now
886ed19bfeba...
886ed19bfeba2b8084cffe9b361bcc754dcd63f2
Sergei Golubchik
C/C fixup resumption
883f28814226...
883f288142266d17da7036b47e913d2d7fcf6cd8
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 DEFAULT 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 at 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.
862420083dfc...
862420083dfc77f757fcd9a74897a9f1f2ca46f1
Sergei Golubchik
MDEV-40445 TLS session resumption (wolfssl)

* enable HAVE_SESSION_TICKET to allow resumption
* enable OPENSSL_ALL+KEEP_PEER_CERT to keep peer cert in the ticket,
  otherwise REQUIRE SUBJECT doesn't work after resumption
* disable OPENSSL_EXTRA which was enabled as a replacement
  when OPENSSL_ALL was disabled in 136e8661197
* disable NO_WOLFSSL_STUB to get SSL_CTX_sess_hits/etc stubs
* but they're stubs, always return 0, so add a wolfssl combination to
  the test that checks for these values
846f7b247ec2...
846f7b247ec257f27a262019b67859f7850c510a
Yuchen Pei
MDEV-40168 wip

works:

SET SESSION debug = '+d,test_invisible_index,test_completely_invisible';
create table t1 (c int, j json, key idx ((CAST(j->'$.tags' AS CHAR(6) ARRAY))));
SHOW CREATE TABLE t1;
Table Create Table
t1 CREATE TABLE `t1` (
  `c` int(11) DEFAULT NULL,
  `j` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL CHECK (json_valid(`j`))
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci
show index from t1;
Table Non_unique Key_name Seq_in_index Column_name Collation Cardinality Sub_part Packed Null Index_type Comment Index_comment Ignored
t1 1 invisible1 1 invisible1 A NULL NULL NULL YES BTREE NO
t1 1 idx 1 DB_MVI_1 NULL NULL NULL NULL YES FULLTEXT NO
insert into t1 values (1, '{"tags": [1, 2, 3]}');
DROP TABLE t1;
7f86cfd32785...
7f86cfd3278584e8019d18309cf8587b80c0673b
Teemu Ollakka
MDEV-36926 Print the selected Asio version at configure time

Add REPORT_ASIO_VERSION() to cmake/asio.cmake, which locates the
asio/version.hpp of the Asio actually picked (custom path, system, or
bundled), decodes ASIO_VERSION and prints "Using Asio version
<major>.<minor>.<patch>" so the configure output shows which Asio the
build resolved to.
7f363f983222...
7f363f98322200fae296ae6574f9db118965b06e
Teemu Ollakka
MDEV-36926 Always use asio::io_context in AsioIoService::Impl

asio::io_context exists in all supported Asio versions (1.14.1+), so
drop the ASIO_VERSION < 103300 guards that fell back to the deprecated
asio::io_service typedef for the include and native_type.
7d7575ecbedf...
7d7575ecbedf92a94e04cce24f72967e42bc5d9f
Sergei Petrunia
Fixup: Let PWT_error_handler have pwt_manager as argument,

Split the code to pwt_manager::finalize_parallel_workers
7659bf226c6c...
7659bf226c6c128f20fc5f19d2db71588474c595
Yuchen Pei
MDEV-40168 wip

works:

create table t1 (c int, j json, key idx ((CAST(j->'$.tags' AS CHAR(6) ARRAY))));
SHOW CREATE TABLE t1;
Table Create Table
t1 CREATE TABLE `t1` (
  `c` int(11) DEFAULT NULL,
  `j` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL CHECK (json_valid(`j`)),
  `DB_MVI_1` text CHARACTER SET latin1 COLLATE latin1_bin GENERATED ALWAYS AS (json_extract(`j`,'$.tags')) STORED,
  FULLTEXT KEY `idx` (`DB_MVI_1`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci
DROP TABLE t1;
726748cde03e...
726748cde03e0c08d3a8f85509d03a17cad503b2
Yuchen Pei
MDEV-40168 wip

works:

SET SESSION debug = '+d,test_invisible_index,test_completely_invisible';
create table t1 (c int, j json, key idx ((CAST(j->'$.tags' AS CHAR(6) ARRAY))));
SHOW CREATE TABLE t1;
Table Create Table
t1 CREATE TABLE `t1` (
  `c` int(11) DEFAULT NULL,
  `j` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL CHECK (json_valid(`j`))
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci
show index from t1;
Table Non_unique Key_name Seq_in_index Column_name Collation Cardinality Sub_part Packed Null Index_type Comment Index_comment Ignored
t1 1 invisible1 1 invisible1 A NULL NULL NULL YES BTREE NO
t1 1 idx 1 DB_MVI_1 NULL NULL NULL NULL YES FULLTEXT NO
insert into t1 values (1, '{"tags": [1, 2, 3]}');
DROP TABLE t1;
7028e25d0abb...
7028e25d0abb9f9954c069b6611e2461c3ccf620
Rex Johnston
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 join 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.

PWT cleanup: move pwt_worker init into pwt_worker::init_worker_thd()
PWT cleanup: comment-out THD::parallel_worker.
  Instead, add "pwt_worker *worker" member to class PWT_error_handler.
PWT cleanup: introduce/use pwt_worker::cleanup_worker()
PWT cleanup: in pwt_manager, add notify_message_dropped, fix record_event().
  Both of them acquire/release needed mutexes inside the function.
PWT cleanup: rename error_to_queue -> save_error_to_queued_event
PWT Cleanup: Comment-out pwt_worker::COND_worker. It is not used.
PWT Cleanup: Let PWT_error_handler have pwt_manager as argument,
  Split the code to pwt_manager::finalize_parallel_workers
PWT Cleanup: Rename LOCK_pwt_thread->LOCK_pwt_manager,
  make more members private.
PWT Cleanup: privatise pwt_manager components
612651567dcf...
612651567dcf6e96c67a2c05da6776059e64db56
Sergei Golubchik
MDEV-12320 change initial authentication plugin in the server

instead of unconditionally starting the authentication from
the mysql_native_password, start it from the plugin that will most
likely avoid "change plugin" packet (and thus a round-trip). Maintain
counters of what plugins were used to authentify users so far, use
the plugin with the largest count for new connections.

FLUSH PRIVILEGES resets the stats.
5f7ee623dbc3...
5f7ee623dbc33ea775a236f836585b28b1152a0f
Sergei Petrunia
Comment-out pwt_worker::COND_worker. It is not used.
5d7ab420bcac...
5d7ab420bcac349b6c8c1fccd3a3c3b7e49b0503
Sergei Golubchik
MDEV-40445 TLS 1.3 early data (0-RTT)

Assisted-By: Claude:claude-5-opus
5847c1aab087...
5847c1aab0870edb6b1913979ff86a073766f269
Monty
Limit the memory used by GROUP_CONCAT() with ORDER BY

GROUP_CONCAT() with ORDER BY collects all rows of the group in a TREE
and only cuts it down in repack_tree(). The repack was triggered by

  (tree_len >> GCONCAT_REPACK_FACTOR) > thd->gconcat_max_len()

with GCONCAT_REPACK_FACTOR 10, that is when the rows in the tree had
produced 1024 * group_concat_max_len bytes, or 1G with the default
settings. On top of that tree_len only counted the length of the
strings, while the tree costs sizeof(TREE_ELEMENT) + reclength per row.
For GROUP_CONCAT(int_col ORDER BY int_col) that is about 40 bytes per
row against 6 bytes of result, so the tree had grown to several GB
before the first repack. In practice the server ran out of memory
first and the repack code was close to never used.

The tree is now limited by the memory it has really allocated,
tree->allocated, instead of by the length of the strings it holds.
The limit is MY_MAX(thd->ram_limitation(), thd->gconcat_max_len()) and
is never set so low that the tree can not hold a few rows.

repack_tree() builds a new tree while the old one is still in memory,
so the peak usage is the size we start the repack at plus the size we
copy to. To keep the sum within the limit it is split into
GCONCAT_TREE_PARTS parts; the repack starts when
GCONCAT_TREE_REPACK_PARTS of them are used and copies to the remaining
part. The part we do not copy to is also the room the tree has to grow
before the next repack, which keeps the repacks amortized.

Other changes:

- tree_len is removed. It was only read by the old trigger.

- repack_tree() decided that it had run out of memory by testing
  st.len <= st.maxlen after the walk. That test was only valid because
  the old trigger guaranteed that a complete copy had to overshoot
  st.maxlen. A repack triggered by memory can complete the walk with
  st.len far below st.maxlen, which would have failed the query with a
  wrong out of memory error. There is now an explicit flag for it.

- The length that decides which rows to keep now also counts the
  separator that is put between two rows, so that it matches what
  val_str() will produce.

- When the memory limit stops the copy, the result becomes shorter
  than group_concat_max_len. dump_leaf_key() can not detect this, as
  the result never reaches the maximum length. This is now remembered
  in result_cut and reported to the user.

- All cut value reporting is moved to val_str(); dump_leaf_key() only
  marks that the result was cut. This removes the need to clear the
  truncated flag of table->blob_storage to avoid a duplicated warning,
  and gives one warning per group also when val_str() is called more
  than once for the same group, which repeated the warning before.

- Added a function comment for repack_tree() that describes where the
  rows are cut away and why building a copy frees memory.

Co-author: Arcadiy Ivanov <[email protected]>
- Fixed a bug in copy_tree()
4e027945e812...
4e027945e81201c2ecf204aea04e4423c0b4869d
Sergei Golubchik
cleanup: redo thd_create_random_password() from thd_rnd service.

* it was only used in sql_acl.cc to generate scramble, not used
  by plugins
* rename to thd_get_session_nonce() that explicitly generates
  session nonce (or "scramble")
* the function returns the existing nonce if it was already
  generated, or generates and saves it in THD, it always does the full
  nonce length, only uses characters in a given range, zero-terminates.
* incompatible change, service version is bumped to 2.0
* parsec also uses thd_get_session_nonce() now
4cadb3c2ce3e...
4cadb3c2ce3eaf95e5baf74c97b216414a77b803
Jan Lindström
Bump version to 26.4.28
481b3f17c30b...
481b3f17c30be3ba543419ef396cd4c7e4700e81
Sergei Golubchik
MDEV-40445 TLS 1.3 early data (wolfssl)

Compiles with WolfSSL but hits protocol errors.
Disable 0-RTT for WolfSSL for now - compile it off, simply
setting SSL_CTX_set_max_early_data(ssl, 0) is not enough.
35911eb97018...
35911eb97018ec91f45184583ad3ef9f78e73c3e
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.
326815657c60...
326815657c60a73fbf8a7d9acc6c9f8ef73e7aa9
Sergei Petrunia
Rename LOCK_pwt_thread->LOCK_pwt_manager, make more members private.
2ecc6b3ebdd8...
2ecc6b3ebdd8cc99415c0c4e6db797f9b189097f
Sergei Golubchik
test that counts number of roundtrips in various situations
2a20601a6e38...
2a20601a6e389d9f728373f439ec9971d265d88e
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.
26fb641adf11...
26fb641adf1184e28aa7989e7765aca77b2e5362
Sergei Golubchik
change_user test in plugins.parsec
154aa7debe82...
154aa7debe8211da4d8f5225f35720a7d27bf0c6
Jan Lindström
Bump Galera version to 26.4.28
135c46e1b786...
135c46e1b786bb46d620dc1e38ac82415425113a
Alexey Yurchenko
MDEV-38920 ensure EVS install timeout stays between suspect and inactive

The view-install timeout must satisfy
  suspect_timeout < install_timeout < inactive_timeout
with at least one keepalive (retrans) period between neighbours. In particular
install_timeout below suspect_timeout causes a view install to be abandoned
before a silent node can even be suspected, which can drive an otherwise
healthy majority to non-primary.

The ordering cannot be enforced strictly - old configurations must still
start - so:
(a) if install_timeout is outside [suspect+retrans, inactive-retrans],
    set it to (suspect_timeout + inactive_timeout)/2;
(b) log a warning if that overrides an explicitly configured install_timeout;
(c) log a warning if (inactive_timeout - suspect_timeout) < 2*retrans_period,
    i.e. the window is too narrow.

Implemented in gcomm::evs::Proto::sanitize_install_timeout(). It is invoked
from the Proto constructor (config load) and from set_param() whenever
suspect/inactive/keepalive/install timeouts change at runtime, so a runtime
reconfiguration cannot re-introduce install_timeout < suspect_timeout.
The helper does not touch timers (state is S_CLOSED during construction).
callers reset T_INSTALL when it adjusts the value.
12e0c84b5e38...
12e0c84b5e385616013c6712fe3fa32139db9854
Marko Mäkelä
fixup! c67768bb802cdd00bf604ae6fde08f896df1ce1b
0c13349e1bc2...
0c13349e1bc25258404561d8bb15ba40ab346c74
Monty
MDEV-40765 Assertion `"unexpected references" == 0' failed upon failing CREATE OR REPLACE

There was a few reasons for this failure:
- There was no timeout for the mdl_lock in the ddl log in
  execute_rename_table. This is needed to protect against a concurrent
  purge in InnoDB. If the purge would be running, the ddl would call
  rename_table without a ddl protection the assert could happen.
- InnoDB locked the original table name in purge, not the temporary
  name used to cache the table in case of rollback. The effect is
  that if a purge happens during rename the assert could happen.
- The table was a partitioned and the detection of partitioned tables
  did not take into account temporary #sql-create- prefixed tables.

Other things:
- The code in execute_rename_table() assumes that InnoDB never holds
  a MDL lock for more more than a few milliseconds. I am using a timeout
  for 10 seconds, just in case. In practice this timeout should be very
  short.
- Added a 10 second timeout for the MDL lock in execute_drop_table()
- Removed mysql_mutex_unlock(&LOCK_gdl) / mysql_mutex_lock(&LOCK_gdl)
  around calls to binlog as these are unsafe. The binlog code uses
  global variables that needs protection from other callers.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Mon 24 Aug 2026 09:00:56 (UTC)