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
fcd8492dd45f...
fcd8492dd45f7202261ca005bbf28a2677a5938b
Sergei Golubchik
s390x
e0cb0291d568...
e0cb0291d568c65820729d80c24182c70aaa92c4
Sergei Golubchik
s390x
dfde0ab8f6d3...
dfde0ab8f6d3d03fc299ed95a309cec5b9365410
PranavKTiwari
dds
da80cfa91584...
da80cfa9158454ea6442ea0bc0e2c5a3cd3f8366
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.
cd8742291c7c...
cd8742291c7cd178987cc5da2ec80abe7adcbea8
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.
cb35095ffcd7...
cb35095ffcd7defbee4dc580ed29351c55b1f8e3
Vladislav Vaintroub
Unify synchronous and asynchronous I/O; enable Schannel async

The non-blocking (async) API kept a complete parallel I/O stack next to
the synchronous one: async_read/async_write pvio methods,
ma_pvio_read_async/ma_pvio_write_async, and per-backend
ma_tls_read_async/ma_tls_write_async, each re-implementing the
"non-blocking attempt + my_context_yield() on would-block" loop.

But ma_pvio_wait_io_or_timeout() already yields the fiber in async mode.
Now that the socket is always non-blocking and the synchronous read/write
loops wait through it, the two paths are structurally identical - the only
difference is whether the wait blocks the thread (poll/select) or suspends
the fiber (yield), which is exactly what wait_io_or_timeout already decides.

So route the synchronous pvio_socket_read/write waits through
ma_pvio_wait_io_or_timeout() and drop the entire parallel async stack:

- remove async_read/async_write from the pvio method table (and the
  socket/shmem/npipe implementations)
- remove ma_pvio_read_async/ma_pvio_write_async and the async branches
  in ma_pvio_read/ma_pvio_write
- remove ma_tls_read_async/ma_tls_write_async (openssl, gnutls),
  ma_tls_async_check_result, and the IS_PVIO_ASYNC_ACTIVE branches in the
  OpenSSL BIO and GnuTLS push/pull callbacks - they now just call the
  blocking pvio read/write, which yields under the hood
- remove the now-unused IS_BLOCKING_ERROR macro

This also enables async for Schannel: ma_pvio_read/write no longer special
-case !HAVE_SCHANNEL, and Schannel already funnels all socket I/O through
pvio->methods->read/write, so it now suspends/resumes like the others.

Named pipe and shared memory cannot suspend/resume (no pollable socket).
Previously async over them errored on the first read (the async_read
method was NULL -> CR_ASYNC_NOT_SUPPORTED in ma_pvio_read_async). That
guard is gone with the parallel stack, so reject MYSQL_OPT_NONBLOCK over
these transports up front in mysql_real_connect() with the same
CR_ASYNC_NOT_SUPPORTED, instead of silently running synchronously and
blocking the caller's event loop. The ordinary blocking API is unaffected.

Tested:
- main.mysql_client_test_nonblock (the full mysql_client_test suite run
  through the non-blocking start/cont API) passes
- mtr unit suite: all 21 unit.conc_* pass (incl. unit.conc_async)
- the async unit test run directly over forced TLS with both OpenSSL and
  GnuTLS clients (test_async = 100 async connect+handshake+query+close
  iterations) passes, confirming the fiber yields correctly through the
  TLS stack

Co-Authored-By: Claude Opus 4.8 <[email protected]>
c077ec913084...
c077ec91308465c2887a06c1dc7b7f86cdf0c325
Pekka Lampio
MDEV-40279 galera.tmp_space_usage test failure

The MTR test galera.tmp_space_usage printed the exact Tmp_space_used /
Max_tmp_space_used byte counts. These come from the binlog cache
temporary file, whose size depends on binary log event encoding and
thus varies across platforms and builds, making the test fail
(e.g. 101706 vs the recorded 102054).

Rewrite the test to check only the invariants the fix is about, as is
already done in main.tmp_space_usage: after the inserts Tmp_space_used
is non-zero and equals Max_tmp_space_used, and after change_user
Tmp_space_used is reset to 0 while Max_tmp_space_used is preserved.

Co-Authored-By: Claude Opus 4.8
bd0b72461de4...
bd0b72461de42c7ea0d615b8a2e9b2a4369f2a48
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 not passing null to
Item_func_not::fix_fields() when caling it from
st_select_lex::pushdown_from_having_into_where()
bbc772f2f3e5...
bbc772f2f3e570bc4723f58485ec247e8e90a6ef
Vladislav Vaintroub
MDEV-37996 CMake: MariaDB:: targets for bundled-or-system libraries

Stop overwriting the standard find_package() result variables (ZLIB_FOUND,
ZLIB_LIBRARIES, ZLIB_INCLUDE_DIR(S), ...), this breaks vcpkg.

Provide namespaced INTERFACE targets that point at either the bundled or
the system library and carry their include directories (and, for SSL, the
compile definitions)

  MariaDB::zlib, MariaDB::OpenSSL, MariaDB::pcre2-8, MariaDB::pcre2-posix,
  MariaDB::fmt, MariaDB::readline

Link these consistently instead of the scattered ${*_LIBRARIES} and
${*_INCLUDE_DIR(S)} variables sprinkled across the tree.

Bundled pcre2-posix depends on pcre2-8 so the static link order is correct
for consumers that link only posix.

wolfssl carries its own usage requirements (HAVE_WOLFSSL,
WOLFSSL_USER_SETTINGS); MariaDB::OpenSSL keeps only HAVE_OPENSSL.

Update libmariadb to 3.3 (47a31a98): handles MariaDB::zlib as a submodule.
b42036c432dd...
b42036c432dd56527cb9b6a45b31278835135895
Vladislav Vaintroub
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
b4040984305a...
b4040984305a052daaac41cda0e0a475f8a3e489
PranavKTiwari
Incorporated CRC.
ae0278fb7454...
ae0278fb74549c0528e7caca7c352bb015b615dd
Sergei Golubchik
MDEV-40312 SHOW CREATE SERVER incorrect quoting

quote protocol name and option names
9c3918cc3170...
9c3918cc3170bde3d7dd38ab274f4371027a4c89
Vladislav Vaintroub
Unify synchronous and asynchronous I/O; enable Schannel async

The non-blocking (async) API kept a complete parallel I/O stack next to
the synchronous one: async_read/async_write pvio methods,
ma_pvio_read_async/ma_pvio_write_async, and per-backend
ma_tls_read_async/ma_tls_write_async, each re-implementing the
"non-blocking attempt + my_context_yield() on would-block" loop.

But ma_pvio_wait_io_or_timeout() already yields the fiber in async mode.
Now that the socket is always non-blocking and the synchronous read/write
loops wait through it, the two paths are structurally identical - the only
difference is whether the wait blocks the thread (poll/select) or suspends
the fiber (yield), which is exactly what wait_io_or_timeout already decides.

So route the synchronous pvio_socket_read/write waits through
ma_pvio_wait_io_or_timeout() and drop the entire parallel async stack:

- remove async_read/async_write from the pvio method table (and the
  socket/shmem/npipe implementations)
- remove ma_pvio_read_async/ma_pvio_write_async and the async branches
  in ma_pvio_read/ma_pvio_write
- remove ma_tls_read_async/ma_tls_write_async (openssl, gnutls),
  ma_tls_async_check_result, and the IS_PVIO_ASYNC_ACTIVE branches in the
  OpenSSL BIO and GnuTLS push/pull callbacks - they now just call the
  blocking pvio read/write, which yields under the hood
- remove the now-unused IS_BLOCKING_ERROR macro

This also enables async for Schannel: ma_pvio_read/write no longer special
-case !HAVE_SCHANNEL, and Schannel already funnels all socket I/O through
pvio->methods->read/write, so it now suspends/resumes like the others.

Named pipe and shared memory cannot suspend/resume (no pollable socket).
Previously async over them errored on the first read (the async_read
method was NULL -> CR_ASYNC_NOT_SUPPORTED in ma_pvio_read_async). That
guard is gone with the parallel stack, so reject MYSQL_OPT_NONBLOCK over
these transports up front in mysql_real_connect() with the same
CR_ASYNC_NOT_SUPPORTED, instead of silently running synchronously and
blocking the caller's event loop. The ordinary blocking API is unaffected.

Tested:
- main.mysql_client_test_nonblock (the full mysql_client_test suite run
  through the non-blocking start/cont API) passes
- mtr unit suite: all 21 unit.conc_* pass (incl. unit.conc_async)
- the async unit test run directly over forced TLS with both OpenSSL and
  GnuTLS clients (test_async = 100 async connect+handshake+query+close
  iterations) passes, confirming the fiber yields correctly through the
  TLS stack

Co-Authored-By: Claude Opus 4.8 <[email protected]>
9b6fdee3456d...
9b6fdee3456df8e979f91ffdd727ba85fc491442
Dave Gosselin
MDEV-33524:  marked_for_read assertion with virtual column

A couple of things interact in this scenario.

1. A virtual column whose value depends on session state, such as a
VCOL calling DATE_FORMAT, has fix_fields (via fix_expr) run on it
again before each INSERT.  For a table reused from the cache this runs in
Vcol_expr_context before setup_tables sets the table map.  The test
first opens t1 with a SELECT that fails before setup_tables, leaving
it cached with map zero.

2. When the connection character set needs conversion, CONCAT (more
generally, any charset aggregation) wraps that column in a charset
converter.  The converter evaluates any argument reported as
constant, so it calls val_str() on the column as part of
fix_fields, before a row exists and without the column in the read
set.  On DEBUG builds this fails the marked_for_read assertion;
otherwise it reads an unread column.

Consequently:
When a table instance is opened, fix_fields runs with table->map
already nonzero, but the fix_fields (via fix_expr) call from vcol_fix_expr
did not have it nonzero; so set table->map=1 during Vcol_expr_context::init.
The original Vcol_expr_context::init() (MDEV-24176) called
init_lex_with_single_table, which set table->map= 1 as a side effect.
A later merge of 10.2 into 10.3 (6f6c74b0d18) replaced that call with
a backup of table->expr_arena, dropping the side effect.
The destructor of the Vcol_expr_context will reset the map back to its
original value.
973b68af9876...
973b68af98769082207a2a765ac1d0f9a7827e59
PranavKTiwari
MDEV-38839: Assertion `(thd->state_flags & Open_tables_state::BACKUPS_AVAIL) || !thd->has_pending_row_events()' failed in close_thread_tables on CREATE TABLE

Problem:
CREATE TABLE ... SELECT ... FOR UPDATE involving a MyISAM temporary table can trigger an assertion in close_thread_tables() when binary logging is enabled in MIXED mode.

Cause:
MyISAM temporary tables do not support row-level locking, so FOR UPDATE acquires a write lock even for read-only access. This causes the table to be incorrectly classified as a write operation, preventing binlog_truncate_trx_cache() from running and ultimately triggering an assertion.

Fix:
Update decide_logging_format() to check tbl->updating and distinguish actual writes from read-only access. For read-only access to temporary non-transactional tables, mark the statement as STMT_READS_TEMP_NON_TRANS_TABLE instead of treating it as a write. This prevents incorrect write classification and avoids the assertion failure.
96191907e964...
96191907e964258cbf27f8cc52a9abdc0c0bf367
Dave Gosselin
MDEV-33524:  marked_for_read assertion with virtual column

vcol.vcol_misc deadlocks under --view-protocol at the
FLUSH TABLES WITH READ LOCK block.  The main connection holds
the global read lock.  The SELECT COUNT(*) FROM t1 query becomes
CREATE OR REPLACE VIEW on a separate connection, and that DDL
blocks on the read lock and never returns.  So the same mysqltest
client never reaches unlock tables.  The fix is to wrap only that
one SELECT in the view_protocol guards.
86fc88f4d2d6...
86fc88f4d2d6dd3bbfe88d0e050f4ced8edcee60
Sergei Golubchik
MDEV-30041 don't set utf8_is_utf8mb3 by default in the old-mode
84c246ca5387...
84c246ca5387c0611f75097136ff4f4bea092aa3
Pekka Lampio
MDEV-40279  Further improvements

Removed unnecessary --enable/disable_query_log statements.
82dad265c5c7...
82dad265c5c7d3cf6536ea4937c9fd5cfe4abe58
Dmitry Shulga
MDEV-37086 Service crashed on procedure call

Extra tests were added
7c7221cfc7dd...
7c7221cfc7dd85e5c9c96131db11f1d5f145ab8e
Vladislav Vaintroub
CONC-828 Always use non-blocking sockets

Drop setsockopt, it creates non-portable problems.
We already can do timeouts portably via non-blocking and poll/select.

Also, make sure SSL libraries use underlying pvio methods,
like they do for Schannel already. it is important, also for timeout handling,
and simplifies architecture quite a bit.

So, no more set_fd, but BIO and gnutls push/pull callbacks.
71d1179b5959...
71d1179b59595656b0f4fbfbe3d2e459a9db8545
Vladislav Vaintroub
Fix bundled pcre2 static link order (buildbot fulltest regression)

pcre2-posix calls into pcre2-8, and as bundled static libs the linker
resolves pcre2_pattern_info_8 only if pcre2-8 comes after pcre2-posix.
mariadb-test-embedded links mysqlserver, which also pulls pcre2-8, so
CMake de-duplicated the explicit trailing pcre2-8 and left it before
pcre2-posix -> undefined reference. Declare pcre2-posix -> pcre2-8 as an
interface dependency so the order is always correct (also fixes the
mariadb-backup case that links only pcre2-posix).
61cc2c83b4ef...
61cc2c83b4ef7cce8d95bad73f4e4547540cb4a0
Dave Gosselin
MDEV-33524:  marked_for_read assertion with virtual column

A couple of things interact in this scenario.

1. A virtual column whose value depends on session state, such as a
VCOL calling DATE_FORMAT, has fix_fields (via fix_expr) run on it
again before each INSERT.  For a table reused from the cache this runs in
Vcol_expr_context before setup_tables sets the table map.  The test
first opens t1 with a SELECT that fails before setup_tables, leaving
it cached with map zero.

2. When the connection character set needs conversion, CONCAT (more
generally, any charset aggregation) wraps that column in a charset
converter.  The converter evaluates any argument reported as
constant, so it calls val_str() on the column as part of
fix_fields, before a row exists and without the column in the read
set.  On DEBUG builds this fails the marked_for_read assertion;
otherwise it reads an unread column.

Consequently:
When a table instance is opened, fix_fields runs with table->map
already nonzero, but the fix_fields (via fix_expr) call from vcol_fix_expr
did not have it nonzero; so set table->map=1 during Vcol_expr_context::init.
The original Vcol_expr_context::init() (MDEV-24176) called
init_lex_with_single_table, which set table->map= 1 as a side effect.
A later merge of 10.2 into 10.3 (6f6c74b0d18) replaced that call with
a backup of table->expr_arena, dropping the side effect.
The destructor of the Vcol_expr_context will reset the map back to its
original value.
4b1548e9b9ab...
4b1548e9b9ab4fe7d548335302ccbc465745dd9c
bsrikanth-mariadb
MDEV-16462: explain format=json produces illegal json text

The attached_condition field of the produced json text had
"String with illegal unicode symbol" instead of the proper unicode
value.

The reason is that, the item field when being written to the json
writer in write_item(), used a String with charset my_charset_bin,
and that prevented the string from being escaped.

Solution is to change the charset to utf8mb4, and also use
writer->add_escaped_str(...), instead of writer->add_str(...);
48f008ff02ac...
48f008ff02ace4a15fefa49646b6fd741fafc993
Vladislav Vaintroub
CONC-828 Remove pvio blocking/is_blocking methods

Follow-up cleanup to "always use non-blocking sockets": now that the
socket is non-blocking for its whole lifetime, the mode-switching
machinery is dead weight, so remove it.

- Drop the blocking() and is_blocking() pvio methods, the
  ma_pvio_blocking()/ma_pvio_is_blocking() wrappers and the per-plugin
  implementations (socket, shmem, npipe).
- Create the socket non-blocking from the start: a new_nonblocking_socket()
  wrapper around socket() sets O_NONBLOCK/FIONBIO immediately, so the fd
  is never blocking at any point in its lifetime. Replaces the old
  per-operation mode toggling; the connect helpers no longer touch it.
- Remove the Windows-only WIN_SET_NONBLOCKING macro and all its call
  sites in mariadb_async.c - it only existed to work around MSG_DONTWAIT
  not being available on Windows.
- Remove MSG_DONTWAIT usage entirely (the socket is already
  non-blocking). The synchronous pvio_socket_read/write loop over the
  ma_recv()/ma_send() primitives with poll()/select(); the async_read/
  async_write methods stay single non-blocking attempts (the fiber yield
  on would-block remains in ma_pvio_read_async()/ma_pvio_write_async()).
- Fold the three identical EAGAIN/EWOULDBLOCK checks (pvio_socket,
  openssl, gnutls) into a single ma_socket_wouldblock() helper in
  ma_global.h, next to the SOCKET_E* definitions.
- Drop the now-unconditional GNUTLS_EXTERNAL_TRANSPORT define and its
  #ifdef guards in gnutls.c; routing TLS through the pvio methods is the
  only mode, so the dead gnutls_transport_set_int() branch goes away.
48310aaa3188...
48310aaa318814fb50cc07af5c10576c5a8fc84e
PranavKTiwari
dds
48227e1cde4c...
48227e1cde4cd8aa77a168bab016e3c48a53c7dc
Vladislav Vaintroub
Update libmariadb to 3.3 (47a31a98)

Pulls the connector fix that removes the bogus stmt_fetch_to_bind length
checks. Without it, connect.bson_udf/json_udf and wide decimal fetches
fail with error 102 (CR_MALFORMED_PACKET) under --ps-protocol.
47a31a98750f...
47a31a98750fd7c805ba67414c6d3df787ce8b2c
Vladislav Vaintroub
Remove length checks in mthd_stmt_fetch_to_bind, keep only the sentinel

Commit dcd0a343 added checks that reject a row as CR_MALFORMED_PACKET
based on server-declared lengths -- the field display width
(field->length) and a hardcoded maximum decimal string length. Both
reject valid data under --ps-protocol:

- field->length is result-set metadata, unrelated to the bytes on the
  wire and routinely large for computed expressions and UDFs; it broke
  connect.bson_udf / connect.json_udf with error 102.
- the decimal cap is a copy of a server-internal limit (already bumped
  67 -> 83 -> 121) that goes stale whenever the server raises precision,
  and it guards nothing: a DECIMAL is fetched as a string and converted
  with bounded parsing/copies, so any in-packet length is handled safely.

The sentinel (data_len > remaining packet space) is the real and only
malformed-packet guard the row data needs. Remove both checks, the now
unused MAX_ZEROFILL_LEN / MAX_DECIMAL_LEN, and the test case that
asserted the removed display-length behaviour.
  • 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
44ea7d0f1105...
44ea7d0f1105dec20bf4826bca0af83f6be5b081
forkfun
MDEV-40303 SIGSEGV in Item_field::type_handler() on PS re-execution

Re-executing a prepared statement that reads a derived-table column
holding a scalar UNION subquery crashed the server: between executions
st_select_lex_unit::cleanup() frees union_result and sets 'cleaned' but
leaves 'prepared' set, so on re-fix set_row() walks a stale item_list
whose Item_field::field are NULL.

Fix: prepare() re-prepares a cleaned unit instead of treating it as
still prepared.
3041efc1dfc6...
3041efc1dfc64e861d0a3e0e9250365103d2407e
bsrikanth-mariadb
MDEV-16462: explain format=json produces illegal json text

The attached_condition field of the produced json text had
"String with illegal unicode symbol" instead of the proper unicode
value.

The reason is that, the item field when being written to the json
writer in write_item(), used a String with charset my_charset_bin,
and that prevented the string from being escaped.

Solution is to change the charset to utf8mb4, and also use
writer->add_escaped_str(...), instead of writer->add_str(...);
2e055c94a9b2...
2e055c94a9b2c0521ad105613f6bb315dc34c67f
Alexander Barkov
MDEV-37086 Service crashed on procedure call

sp_pcontext::retrieve_field_definitions() did not work correctly
in all combinations of mixed declarations of variables and cursors
with parameters.

Rewriting it in a 2-way merge style algorithm.
- The first tape is the array of variables in m_vars.
- The second tape is the children contexts in m_children,
  also containing variables and cursor parameters.
2921a9333eda...
2921a9333edacbf3122c31d91d3b4df6a55c6145
Sergei Golubchik
CREATE SERVER: fix option parsing to support backticks properly

CREATE SERVER used to:
* support arbitrary options in backticks and not in backticks
* hard-coded historical options worked *only* without backticks
* PORT range was different when given as a number or a string

all that is fixed, unused keywords are removed
23e1933ebc06...
23e1933ebc060ed853cb11b48272dbde72fb3708
Daniel Black
MDEV-29542: enable --view-protocol on set_password test

By using the case correct User,Host,Password from the
mysql.user view.
21783af7b9ee...
21783af7b9ee85f4ad3faf52664a7e20914377b7
Vladislav Vaintroub
CONC-828 Remove pvio blocking/is_blocking methods

Follow-up cleanup to "always use non-blocking sockets": now that the
socket is non-blocking for its whole lifetime, the mode-switching
machinery is dead weight, so remove it.

- Drop the blocking() and is_blocking() pvio methods, the
  ma_pvio_blocking()/ma_pvio_is_blocking() wrappers and the per-plugin
  implementations (socket, shmem, npipe).
- Create the socket non-blocking from the start: a new_nonblocking_socket()
  wrapper around socket() sets O_NONBLOCK/FIONBIO immediately, so the fd
  is never blocking at any point in its lifetime. Replaces the old
  per-operation mode toggling; the connect helpers no longer touch it.
- Remove the Windows-only WIN_SET_NONBLOCKING macro and all its call
  sites in mariadb_async.c - it only existed to work around MSG_DONTWAIT
  not being available on Windows.
- Remove MSG_DONTWAIT usage entirely (the socket is already
  non-blocking). The synchronous pvio_socket_read/write loop over the
  ma_recv()/ma_send() primitives with poll()/select(); the async_read/
  async_write methods stay single non-blocking attempts (the fiber yield
  on would-block remains in ma_pvio_read_async()/ma_pvio_write_async()).
- Fold the three identical EAGAIN/EWOULDBLOCK checks (pvio_socket,
  openssl, gnutls) into a single ma_socket_wouldblock() helper in
  ma_global.h, next to the SOCKET_E* definitions.
- Drop the now-unconditional GNUTLS_EXTERNAL_TRANSPORT define and its
  #ifdef guards in gnutls.c; routing TLS through the pvio methods is the
  only mode, so the dead gnutls_transport_set_int() branch goes away.
1fff140f0c25...
1fff140f0c25f6a5b2f6fd0b5ef6b6c50d60e913
Daniel Black
MDEV-40313 mariadb client creates `.mariadb_histor` instead of `.mariadb_history`

`histfile_size` in `client/mysql.cc` is calculated using the string
"/.mysql_history" (15 chars) rather than "/.mariadb_history" (17 chars).

Because the buffer is only allocated to that shorter length, the resulting
filename is truncated by 2 characters.

Thanks David Lu for the bug report and diagnosis.
1c93509db4f1...
1c93509db4f1bcc63c5459ec1b7851d322b1c118
Dave Gosselin
MDEV-33524:  marked_for_read assertion with virtual column

vcol.vcol_misc deadlocks under --view-protocol at the
FLUSH TABLES WITH READ LOCK block.  The main connection holds
the global read lock.  The SELECT COUNT(*) FROM t1 query becomes
CREATE OR REPLACE VIEW on a separate connection, and that DDL
blocks on the read lock and never returns.  So the same mysqltest
client never reaches unlock tables.  The fix is to wrap only that
one SELECT in the view_protocol guards.
194c6801fc6e...
194c6801fc6e8d0b0960adc011fa29c9e992861f
Raghunandan Bhat
MDEV-40316: Infer: PULSE_RESOURCE_LEAK in connect

Problem:
  Infer found file descriptors left open on some error code paths in
  connect storage engine.

Fix:
  Close file descriptors on error before returning.
0d797efac4ce...
0d797efac4cef0793132acb62e446a7d81c6e6d6
Dmitry Shulga
MDEV-37086 Service crashed on procedure call

Extra tests were added
08f8ff0b4db9...
08f8ff0b4db93324f5b6d0edbcdfa57238149fed
Vladislav Vaintroub
CONC-828 Always use non-blocking sockets

Drop setsockopt, it creates non-portable problems.
We already can do timeouts portably via non-blocking and poll/select.

Also, make sure SSL libraries use underlying pvio methods,
like they do for Schannel already. it is important, also for timeout handling,
and simplifies architecture quite a bit.

So, no more set_fd, but BIO and gnutls push/pull callbacks.
0617cf2ab5fc...
0617cf2ab5fc37f49b25c22524c909f26069bd44
Teemu Ollakka
MDEV-40222 Prevent MTR hang when waiting for wsrep_ready

A query against a server that is up but wedged can connect yet never
return, so the loop-count bound in wait_wsrep_ready() did not actually
limit the wait and MTR could hang until the suite timeout fired.

Add an optional $timeout to run_query_output(): the mysql client is
now spawned via My::SafeProcess->new and waited for with
wait_one($timeout), killing the client and returning non-zero if it
does not finish in time.

Bound wait_wsrep_ready() by a wall-clock deadline (start_timer)
instead of a loop count, and pass the remaining time to each query so
no single hung client can exceed the overall server startup budget.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Thu 09 Jul 2026 14:23:02 (UTC)