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
fd91ec6f2fbd...
fd91ec6f2fbde5738c12105aa5c7c455669d55a6
Yuchen Pei
MDEV-15621 Auto add RANGE COLUMNS partitions by interval

Allow auto partitioning by interval in PARTITION BY RANGE COLUMNS

PARTITION BY RANGE COLUMNS (col_name)
INTERVAL interval [AUTO]
(
  PARTITION partition_name VALUES LESS THAN (value)
  [, PARTITION partition_name VALUES LESS THAN (value) ... ]
)

where

- col_name is the name of one column of type DATE or DATETIME or
  TIMESTAMP

- at least one partition is supplied, and the highest partition cannot
  have MAXVALUE range

- INTERVAL interval is a positive time interval. it can be mariadb
  format or oracle NUMTODSINTERVAL/NUMTOYMINTERVAL format. Like
  versioning, the smallest unit is second, i.e. no subsecond like
  microsecond.

- DATE column cannot have interval with values less than a day

When performing DML on such a table, it will first add partitions
by the specified interval until the partition covers the current time.

Partition addition will not cause an implicit commit like DDL normally
does.

The partitions are named pN.

Otherwise the table behaves exactly the same as a normal RANGE COLUMNS
partitioned table.

Note that TIMESTAMP is not allowed as a type for PARTITION BY RANGE
COLUMNS otherwise.
f4696c811ea3...
f4696c811ea3ab6c2040f706b8c27d37f0a5580c
bsrikanth-mariadb
MDEV-39791: Handle count aggregate optimization for replay purpose

Separately dump into the optimizer context, the count aggregation value
of any one non-nullable column of a table if any are used in the query.
This is only suppoerted for myisam tables.

During opt_sum_query() call, record the count aggregation values into
the optimizer context recorder. Once the context is being stored into
the information_schema table, dump all these recorded values into it.

During replay, parse the count aggregate values and store them in memory.
Later when opt_sum_query() requires the count value, hook the recorded
value from the parsed context.
eb07fefeadc4...
eb07fefeadc41313173c97d594d12c4ab0b313bc
Vladislav Vaintroub
x
e2e57f2c81f9...
e2e57f2c81f9d691947634168a37bf3fdfe530d9
Marko Mäkelä
Correctly copy the last one or two log files
e1a9f4825427...
e1a9f48254278dc56162796413efc0b11c03e84e
ParadoxV5
simplify rpl.rpl_read_new_relay_log_info and merge into it

new description for the eventual squashed commit follows–

---

MDEV-39788 found that the recent refactor on the `main` (now 12.3)
branch missed the (inconsistent) detail that, unlike `@@relay_log_info`,
`@@master_info`’s line count _includes_ the line-count line itself.

This commit extends and simplifies the test
`rpl.rpl_read_new_relay_log_info` to `main.rpl_read_new_info` so it
* Checks this detail to remind future changes of this type of mistakes.
* Covers `@@master_info` as well.

While here, this commit also includes a new-format version
of MDEV-39788’s test to double as the value read check.
e13989fcc137...
e13989fcc1375fbce388ae95e9538e7c452e25a7
Sergei Petrunia
Capture more system variables in optimizer_context: sql_mode
e096bd33c78b...
e096bd33c78baee68af6f7b951e13636e0b92fd0
Marko Mäkelä
fixup! e2e57f2c81f9d691947634168a37bf3fdfe530d9
dd2de01aab25...
dd2de01aab25af3eafe089243aefbb9ff6a3456e
Vladislav Vaintroub
Merge branch '11.4' into 11.8
d622742a15bf...
d622742a15bfbf1e01719a1d0e14576255be064f
copilot-swe-agent[bot]
Address some Copilot concerns

- some force_allow with DENY overwrite flags

- Add a test to checks how SHOW GRANTS behaves if user is granted mysql.*
but denied any table in mysql db.
Expected behavior - own DENY entries now shown, SHOW GRANTS for another
user fails.
d11539dc5b41...
d11539dc5b41daa58342d901dd4a91576a048f16
Yuchen Pei
MDEV-15621 Auto add RANGE COLUMNS partitions by interval

Allow auto partitioning by interval in PARTITION BY RANGE COLUMNS

PARTITION BY RANGE COLUMNS (col_name)
INTERVAL interval [AUTO]
(
  PARTITION partition_name VALUES LESS THAN (value)
  [, PARTITION partition_name VALUES LESS THAN (value) ... ]
)

where

- col_name is the name of one column of type DATE or DATETIME or
  TIMESTAMP

- at least one partition is supplied, and the highest partition cannot
  have MAXVALUE range

- INTERVAL interval is a positive time interval. it can be mariadb
  format or oracle NUMTODSINTERVAL/NUMTOYMINTERVAL format. Like
  versioning, the smallest unit is second, i.e. no subsecond like
  microsecond.

- DATE column cannot have interval with values less than a day

When performing DML on such a table, it will first add partitions
by the specified interval until the partition covers the current time.

Partition addition will not cause an implicit commit like DDL normally
does.

The partitions are named pN.

Otherwise the table behaves exactly the same as a normal RANGE COLUMNS
partitioned table.

Note that TIMESTAMP is not allowed as a type for PARTITION BY RANGE
COLUMNS otherwise.
c90f391acc33...
c90f391acc33fe19f1f4c339448f019436b601ea
Marko Mäkelä
fixup! c0e48fc966d3d3926bade68c7c5bfdb9fe88ad3a
c7baf3df9112...
c7baf3df9112ad7a41033a1031eb95279208a526
Monty
Remove wrong assert in log_event_server.cc

The test for:
DBUG_ASSERT(thd->lex->query_tables != table_list);
does not make any sense:
- table_list is a pointer we just got from malloc)()
- thd->lex->query_tables can point to an existing TABLE_LIST
  or is a pointer to already freed memory.

In 'main' I got the above assert multiple times triggered when
running rpl.rpl_row_img_blobs on a valgrind build. There was
nothing wrong with the allocations, just random change have
malloc return a recently freed pointer.
c5a4c753aefe...
c5a4c753aefea7da0f9bb319665d2bd18783ff7e
Vladislav Vaintroub
MDEV-14443 - address some review comments and rebase against upstream
c3dc2df9d8dc...
c3dc2df9d8dc5c28b81555cd1ba96ce1d5d36343
Monty
Add likely/unlikely to my_b_read/write functions
c24b223a77d2...
c24b223a77d24c523e53a60bd63ca342dee16c91
Sergei Petrunia
MDEV-39368: Run "SET foreign_key_checks=0" on the replay server.

This is to avoid FK mismatch errors.
c2470f120e41...
c2470f120e413228f52cab9e9b0544b9b7c7bc11
Yuchen Pei
MDEV-15621 Auto add RANGE COLUMNS partitions by interval

Allow auto partitioning by interval in PARTITION BY RANGE COLUMNS

PARTITION BY RANGE COLUMNS (col_name)
INTERVAL interval [AUTO]
(
  PARTITION partition_name VALUES LESS THAN (value)
  [, PARTITION partition_name VALUES LESS THAN (value) ... ]
)

where

- col_name is the name of one column of type DATE or DATETIME or
  TIMESTAMP

- at least one partition is supplied, and the highest partition cannot
  have MAXVALUE range

- INTERVAL interval is a positive time interval. it can be mariadb
  format or oracle NUMTODSINTERVAL/NUMTOYMINTERVAL format. Like
  versioning, the smallest unit is second, i.e. no subsecond like
  microsecond.

- DATE column cannot have interval with values less than a day

When performing DML on such a table, it will first add partitions
by the specified interval until the partition covers the current time.

Partition addition will not cause an implicit commit like DDL normally
does.

The partitions are named pN.

Otherwise the table behaves exactly the same as a normal RANGE COLUMNS
partitioned table.

Note that TIMESTAMP is not allowed as a type for PARTITION BY RANGE
COLUMNS otherwise.
bd9c7694fe5e...
bd9c7694fe5e835b63db625d60f07b82d9ce1095
Monty
Avoid strlen() calls in Explain_index_usage and String_list

Use Lex_ident_column* instead of char* as parameters
b7fd588a7c05...
b7fd588a7c05eb46eac945be0c9f3eeacab81897
Sergei Petrunia
main.derived_opt: add a few --disable_replay next_query Need to preserve optimizer trace
a3c6c2fb6412...
a3c6c2fb641209542f46b48fc6905fe707ed1ae0
Monty
Fixed wrong code in ha_perfschema::delete_table()

In case there was no '/' or '\' in the path, *ptr = '\0' would
change data outside of table_path[]

This patch also removes a warning from gcc.
9962acb15110...
9962acb15110d997cfed9971871a26242c0773e8
Yuchen Pei
MDEV-39789 Fix compiling without perfschema
982f0e73563c...
982f0e73563c0b3ee1055ad8af863d34fd41529e
Sergei Petrunia
Capture more system variables in optimizer_context: TIMESTAMP, old_mode.
8ad247220769...
8ad2472207694a0546f1ae40c04824889775c5a7
Vladislav Vaintroub
MDEV-14443 - address some review comments and rebase against upstream
8641e4cbab7c...
8641e4cbab7c91614535164caf400976303c6dca
Arcadiy Ivanov
Add unit test for concurrent blob del_link race condition

Two threads share one `HP_SHARE` via separate `HP_INFO` handles and
do insert/delete cycles with blobs. A `pthread_mutex` serializes all
operations including `hp_flush_pending_blob_free()`, matching what
`ha_heap::external_lock(F_UNLCK)` does under `thr_lock`.

Moving the flush outside the mutex (simulating the unfixed code path
where the flush ran in `heap_reset()` after `thr_lock` release)
reproduces the SIGSEGV crash from concurrent `del_link` corruption.
856af0cae0fc...
856af0cae0fc04a86bd3e7af6522cb594e13860d
Oleg Smirnov
Fix failing tests
82715a044774...
82715a04477440cd2dec6bd1c05aa0e372b5d784
Monty
Fixed potential race condition in heap that could cause crash

In case of "create table(..) engine=heap" there is this possible scenaro:
- T1 deletes a row with a blob, that is stored for a later call to
  hp_flush_pending_blob_free(), and then ends the statement.
- T2 does a write of a new row
- T1 calls hp_close() that calls hp_flush_pending_blob_free()
Now T1 and T2 are both working on the same delete list, which can
cause a crash.

Fix is to call hp_flush_pending_blob_free() at external_unlock
(end of statement) so that T1's blobs are freed before T2 can
get a lock on the table.
7bd7dd284338...
7bd7dd284338c31748066cc137fbb25dda548c97
Sergei Petrunia
MDEV-39412: parse error reading tabs in ranges

Variant 2:
Previous commits have made these fixes:
- Writing JSON does proper escaping,
- Reading JSON doesn't damage characters with wchar_t > 255.

The only thing left to fix is to properly escape the SQL literal when
writing the
  SET @opt_context='json_doc';
statement.

This fixes at least this test: ./mtr --replay-server type_varchar
75cc7c25485f...
75cc7c25485f9248a6fe7646388efd622ab994af
Vladislav Vaintroub
y
708d968af03f...
708d968af03f604b6d997b5386c0112537abfa29
Monty
Remove C++ STL machinery from sql/rpl_*info_file.* and CHANGE MASTER parser

Replaces std::function / std::optional / std::unordered_map /
std::unordered_set / std::string_view and template-heavy code in the
master.info / relay-log.info persistence layer with plain MariaDB
idioms.
- On-disk file format unchanged.
- SQL syntrax unchanged
- No notable test changes, except those for which new error messages was
  added and output from SHOW VARIABLES.

- master_* CLI options moved from inline globals in
  rpl_master_info_file.h to Sys_var_* in sys_vars.cc (READ_ONLY,
  AUTO_SET on use_gtid and heartbeat_period). master_heartbeat_period
  is Sys_var_double (seconds); master_use_gtid is Sys_var_enum. Global
  storage sits outside HAVE_REPLICATION so libmariadbd links.
  - This adds the rpl_master_info variables to SHOW VARIABLES
- Value classes are no longer templates. Persistent renamed to Value;
  Optional_* classes renamed (Uint_value_with_default, Path_value,
  etc.).  has_value flag in the base; is_default()
  non-virtual. Multi-line method bodies moved to new rpl_info_file.cc
  and rpl_master_info_file.cc.
- VALUE_LIST (Mem_fn array) and VALUE_MAP (std::unordered_map)
  replaced by per-instance Value *const value_list[] / value_map[]
  arrays + a static TYPELIB populated at first construction from each
  Value's variable_name. seen-set dedup is now a uint32 bitmask.
- Default handling is not anymore done with using special values.
  Setting a value to default is now done by calling set_default(),
  which sets the has_value member to 0 and stores the default value
  in the variable.
  When reading a value, one does not have to check if the value is
  a default value.
  This makes the interface cleaner and easier to manage.
- CHANGE MASTER TO parser no longer builds std::function lambdas:
  LEX_MASTER_INFO carries mi_used_options / mi_used_default bitmasks
  plus plain value fields; change_master() applies them via bit-test +
  direct copy or set_default(). std::optional<T> and trilean are gone
  from the value class API.
- Heartbeat_period_value::load_from uses my_strtod() instead of
  my_decimal for the on-disk format. from_decimal kept for CHANGE
  MASTER.
- RocksDB #if __cplusplus < 201703L guard at the top of
  rpl_master_info_file.h dropped; header now compiles in C++11.
  cstdint dropped; uint32_t / UINT32_MAX in touched code replaced by
  MariaDB's uint32 / UINT_MAX32. include/my_global.h gains
  INT_BUFFER_SIZE next to LONGLONG_BUFFER_SIZE.
- Pointer-style throughout (T * not T &). Multi-line inline functions
  used in more than one place moved to .cc files per style.

New features:
- SHOW VARIABLES now shows the master default values.
- If there is an wrong value for a row in a master.info file the
  corresponding variable name and the value is now written to the
  error log.

Bug fixes uncovered by the refactor:
- master_ssl_verify_server_cert had a pre-existing inconsistency with
  security implications: the documented default and the Sys_var_mybool
  default are TRUE (validate the master's certificate), but the OLD
  init_ssl_config() set the per-Master_info field to FALSE on RESET
  SLAVE ALL. Concretely: after RESET SLAVE ALL followed by a bare
  CHANGE MASTER TO (no explicit MASTER_SSL_VERIFY_SERVER_CERT), the
  slave would connect with MASTER_SSL=1 enabled but with certificate
  validation silently disabled.
  Fixed by not resetting master_ssl_verify_server_cert in
  RESET SLAVE ALL;
- As some replication setups sets master_ssl_verify_server_cert= 0
  while other does not do that, the expected value used in
  check-testcase.inc "Master_SSL_Verify_Server_Cert No" does not make
  sense.  The value of this variable is now ignored by
  check-testcase.inc
- The old code would fail to read a master info file if there was a new
  variable longer than 23 characters. This is now extended to 80.

Other things
- Size of mariadb (optimize build) shrunk with 1,408,009 bytes
  (Based on 'dec' from the size command)
- Size of code in sql directory did not change notable.
67436841e8c4...
67436841e8c46e2aadf5fe0f5f21fa13a801e6b4
Sergei Petrunia
Fixup for: Make INFORMATION_SCHEMA.OPTIMIZER_CONTEXT.CONTEXT binary
673b0856283f...
673b0856283fdd0059f4cc71aa5eec10e9792322
Monty
Remove C++ STL machinery from sql/rpl_*info_file.* and CHANGE MASTER parser

Replaces std::function / std::optional / std::unordered_map /
std::unordered_set / std::string_view and template-heavy code in the
master.info / relay-log.info persistence layer with plain MariaDB
idioms.
- On-disk file format unchanged.
- SQL syntrax unchanged
- No notable test changes, except those for which new error messages was
  added and output from SHOW VARIABLES.

* master_* CLI options moved from inline globals in rpl_master_info_file.h
  to Sys_var_* in sys_vars.cc (READ_ONLY, AUTO_SET on use_gtid and
  heartbeat_period). master_heartbeat_period is Sys_var_double (seconds);
  master_use_gtid is Sys_var_enum. Global storage sits outside
  HAVE_REPLICATION so libmariadbd links.
  - This adds the rpl_master_info variables to SHOW VARIABLES
* Value classes are no longer templates. Persistent renamed to Value;
  Optional_* classes renamed (Uint_value_with_default, Path_value, etc.).
  has_value flag in the base; is_default() non-virtual. Multi-line method
  bodies moved to new rpl_info_file.cc and rpl_master_info_file.cc.
* VALUE_LIST (Mem_fn array) and VALUE_MAP (std::unordered_map) replaced
  by per-instance Value *const value_list[] / value_map[] arrays + a
  static TYPELIB populated at first construction from each Value's
  variable_name. seen-set dedup is now a uint32 bitmask.
* CHANGE MASTER TO parser no longer builds std::function lambdas:
  LEX_MASTER_INFO carries mi_used_options / mi_used_default bitmasks
  plus plain value fields; change_master() applies them via bit-test +
  direct copy or set_default(). std::optional<T> and trilean are gone
  from the value class API.
* Heartbeat_period_value::load_from uses my_strtod() instead of
  my_decimal for the on-disk format. from_decimal kept for CHANGE MASTER.
* RocksDB #if __cplusplus < 201703L guard at the top of
  rpl_master_info_file.h dropped; header now compiles in C++11.
  cstdint dropped; uint32_t / UINT32_MAX in touched code replaced by
  MariaDB's uint32 / UINT_MAX32. include/my_global.h gains
  INT_BUFFER_SIZE next to LONGLONG_BUFFER_SIZE.
* Pointer-style throughout (T * not T &). Multi-line inline functions
  used in more than one place moved to .cc files per style.

New features:

- SHOW VARIABLES now shows the master default values.
- If there is an wrong value for a row in a master.info file the
  corresponding variable name and the value is now written to the error
  log.

Bug fixes uncovered by the refactor:

- master_ssl_verify_server_cert had a pre-existing inconsistency with
  security implications: the documented default and the Sys_var_mybool
  default are TRUE (validate the master's certificate), but the OLD
  init_ssl_config() set the per-Master_info field to FALSE on RESET
  SLAVE ALL. Concretely: after RESET SLAVE ALL followed by a bare
  CHANGE MASTER TO (no explicit MASTER_SSL_VERIFY_SERVER_CERT), the
  slave would connect with MASTER_SSL=1 enabled but with certificate
  validation silently disabled.
  Fixed by not resetting master_ssl_verify_server_cert in
  RESET SLAVE ALL;
- As some replication setups sets master_ssl_verify_server_cert= 0
  while other does not do that, the expected value used in
  check-testcase.inc "Master_SSL_Verify_Server_Cert No" does not make
  sense.  The value of this variable is now ignored by
  check-testcase.inc

- The old code would fail to read a master info file if there was a new
  variable longer than 23 characters. This is now extended to 80.

Other things
- Size of mariadb (optimize build) shrunk with 1,408,009 bytes
  (Based on 'dec' from the size command)
- Size of code in sql directory is almost identical
5a0b74a31c14...
5a0b74a31c146969b1012082d62fb3efc4edf5a2
Yuchen Pei
MDEV-15621 [refactor] Partitioning cleanup

change p_column_list_val::fixed to a bool
remove redundant end label in partition_info::fix_column_value_functions
5148f029d6df...
5148f029d6df088dde1ad658a75602ce2566964b
Vladislav Vaintroub
Address some Copilot concerns

- some force_allow with DENY overwrite flags

- Add a test to checks how SHOW GRANTS behaves if user is granted mysql.*
but denied any table in mysql db.
Expected behavior - own DENY entries now shown, SHOW GRANTS for another
user fails.
4d0d4556926a...
4d0d4556926ab6d36f25a97d5dbfb22631c1625c
copilot-swe-agent[bot]
Address five Copilot review findings
4b13925ef3a6...
4b13925ef3a610d7a73530c2bcb7041fa8479d7f
Monty
MDEV-39703 mroonga/storage.fulltext_order_natural_language_mode_different
Removed unnessary show status like "Created_tmp%" test
4ab6759ea803...
4ab6759ea8032520acfa68a6f3b9bd50778c6b8c
Yuchen Pei
MDEV-15621 Auto add RANGE COLUMNS partitions by interval

Allow auto partitioning by interval in PARTITION BY RANGE COLUMNS

PARTITION BY RANGE COLUMNS (col_name)
INTERVAL interval [AUTO]
(
  PARTITION partition_name VALUES LESS THAN (value)
  [, PARTITION partition_name VALUES LESS THAN (value) ... ]
)

where

- col_name is the name of one column of type DATE or DATETIME or
  TIMESTAMP

- at least one partition is supplied, and the highest partition cannot
  have MAXVALUE range

- INTERVAL interval is a positive time interval. it can be mariadb
  format or oracle NUMTODSINTERVAL/NUMTOYMINTERVAL format. Like
  versioning, the smallest unit is second, i.e. no subsecond like
  microsecond.

- DATE column cannot have interval with values less than a day

When performing DML on such a table, it will first add partitions
by the specified interval until the partition covers the current time.

Partition addition will not cause an implicit commit like DDL normally
does.

The partitions are named pN.

Otherwise the table behaves exactly the same as a normal RANGE COLUMNS
partitioned table.

Note that TIMESTAMP is not allowed as a type for PARTITION BY RANGE
COLUMNS otherwise.
459a648b62c1...
459a648b62c1d7efe9d0ba087dd6994c51726142
Vladislav Vaintroub
x
3647e9b99303...
3647e9b99303f0464db0052591a058299533b851
Daniel Black
MDEV-39803 RPM dependencies missing from MariaDB-server-galera package

RPM dependencies where not included in cpack build due to incorrect
component name.

Corrects a103be381b38
2b774a07bd74...
2b774a07bd749cac271924add776e856b8ccfbe5
Monty
Remove C++ STL machinery from sql/rpl_*info_file.* and CHANGE MASTER parser

Replaces std::function / std::optional / std::unordered_map /
std::unordered_set / std::string_view and template-heavy code in the
master.info / relay-log.info persistence layer with plain MariaDB
idioms.
- On-disk file format unchanged.
- SQL syntrax unchanged
- No notable test changes, except those for which new error messages was
  added and output from SHOW VARIABLES.

- master_* CLI options moved from inline globals in
  rpl_master_info_file.h to Sys_var_* in sys_vars.cc (READ_ONLY,
  AUTO_SET on use_gtid and heartbeat_period). master_heartbeat_period
  is Sys_var_double (seconds); master_use_gtid is Sys_var_enum. Global
  storage sits outside HAVE_REPLICATION so libmariadbd links.
  - This adds the rpl_master_info variables to SHOW VARIABLES
- Value classes are no longer templates. Persistent renamed to Value;
  Optional_* classes renamed (Uint_value_with_default, Path_value,
  etc.).  has_value flag in the base; is_default()
  non-virtual. Multi-line method bodies moved to new rpl_info_file.cc
  and rpl_master_info_file.cc.
- VALUE_LIST (Mem_fn array) and VALUE_MAP (std::unordered_map)
  replaced by per-instance Value *const value_list[] / value_map[]
  arrays + a static TYPELIB populated at first construction from each
  Value's variable_name. seen-set dedup is now a uint32 bitmask.
- Default handling is not anymore done with using special values.
  Instead setting a value to default is done by calling set_default().
  This makes the interface cleaner and easier to manage.
- CHANGE MASTER TO parser no longer builds std::function lambdas:
  LEX_MASTER_INFO carries mi_used_options / mi_used_default bitmasks
  plus plain value fields; change_master() applies them via bit-test +
  direct copy or set_default(). std::optional<T> and trilean are gone
  from the value class API.
- Heartbeat_period_value::load_from uses my_strtod() instead of
  my_decimal for the on-disk format. from_decimal kept for CHANGE
  MASTER.
- RocksDB #if __cplusplus < 201703L guard at the top of
  rpl_master_info_file.h dropped; header now compiles in C++11.
  cstdint dropped; uint32_t / UINT32_MAX in touched code replaced by
  MariaDB's uint32 / UINT_MAX32. include/my_global.h gains
  INT_BUFFER_SIZE next to LONGLONG_BUFFER_SIZE.
- Pointer-style throughout (T * not T &). Multi-line inline functions
  used in more than one place moved to .cc files per style.

New features:
- SHOW VARIABLES now shows the master default values.
- If there is an wrong value for a row in a master.info file the
  corresponding variable name and the value is now written to the
  error log.

Bug fixes uncovered by the refactor:
- master_ssl_verify_server_cert had a pre-existing inconsistency with
  security implications: the documented default and the Sys_var_mybool
  default are TRUE (validate the master's certificate), but the OLD
  init_ssl_config() set the per-Master_info field to FALSE on RESET
  SLAVE ALL. Concretely: after RESET SLAVE ALL followed by a bare
  CHANGE MASTER TO (no explicit MASTER_SSL_VERIFY_SERVER_CERT), the
  slave would connect with MASTER_SSL=1 enabled but with certificate
  validation silently disabled.
  Fixed by not resetting master_ssl_verify_server_cert in
  RESET SLAVE ALL;
- As some replication setups sets master_ssl_verify_server_cert= 0
  while other does not do that, the expected value used in
  check-testcase.inc "Master_SSL_Verify_Server_Cert No" does not make
  sense.  The value of this variable is now ignored by
  check-testcase.inc
- The old code would fail to read a master info file if there was a new
  variable longer than 23 characters. This is now extended to 80.

Other things
- Size of mariadb (optimize build) shrunk with 1,408,009 bytes
  (Based on 'dec' from the size command)
- Size of code in sql directory did not change notable.
2b20294990f2...
2b20294990f297de63772c7c08f68beb2eb825de
Monty
Fixed bug in rpl.rpl_killed_ddl.result test case

View 'v1' was not always dropped (timeing issue)
0c2f3de1a2d6...
0c2f3de1a2d66fed61488388f5f3da212d582a80
ParadoxV5
MDEV-24646/MDEV-39711: Fix System-Versioned UPDATE with VIRTUAL columns

UPDATEs on System-Versioned Tables used stale data for Row
Format Binary Logging’s after-image, which may be the before-
value (MDEV-39711) or even invalidated memory (MDEV-24646).
BuildBot (0.8.9) working for the MariaDB project.
Page built: Mon 01 Jun 2026 09:53:36 (UTC)