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
f7637ba72e97...
f7637ba72e97e0657ed1f2183037a5a9facb9a7d
Mohammad Tafzeel Shams
MDEV-38079: Crash recovery fails after ALTER TABLE…PAGE_COMPRESSED=1

Issue:
- Instant enabling of page_compressed may cause crash recovery failure.
- FSP_SPACE_FLAGS may not match the actual page format during recovery.

Root Cause:
- Table t has pending writes.
- ALTER TABLE t PAGE_COMPRESSED=1 is executed.
- Some pending pages are written in compressed format, but the server may
  crash before all pages are rewritten.
- During recovery, FSP_SPACE_FLAGS may indicate non-compressed while some
  pages are compressed which results in space ID mismatch.

Fix:
- We go for the simple fix of requiring the table to be rebuilt when the
  page_compressed attribute is changed, because:
  - The page_compressed option is used very rarely.
  - The only motivation of page_compressed=1 is to save space, and space may
    only be saved when all pages of the table are rewritten (table is rebuilt).

- alter_options_need_rebuild(): Enabling page_compressed will require a
  full table rebuild.
f703dad95222...
f703dad952225276780e29dc2f4cc5939238b61b
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Follow-up to fix building with EMBEDDED server. Since support of
events isn't compiled in for embedded server but some stuff from
implementation of events is used for support of triggers, common
source code used both for events and triggers was extracted into
the separate files event_common.cc/event_common.h
eea1fa854a3f...
eea1fa854a3fe084fa70a295483b2e864d615b49
Dave Gosselin
MDEV-38921: Incorrect ORDER BY Result

In the case that we cannot avoid a descending scan and there's no
minimum endpoint (i.e., the minimum endpoint is zero), then clear
the end range on the storage engine.  This is necessary especially
when there are multiple ranges considered and a later range
indicates that there's no minimum endpoint (such as in the attached
test case), thus an earlier range endpoint must be removed/cleared.
e20d78c1ac92...
e20d78c1ac924664eaed73729bd093610b4994da
forkfun
MDEV-26112 STR_TO_DATE should work with lc_time_names
e0f9da296be0...
e0f9da296be06feacb3fd1614ce7dd6ebde827e9
Marko Mäkelä
squash! 99959b558e7089f6611d0cadf0b58b8a608a79b3

In the log_sys.is_mmap_writeable() code path, we assert
and guarantee buf_size == capacity().
e05f8aa722c0...
e05f8aa722c0086a029ec226cdacc0e5760e9d3f
Vladislav Vaintroub
naming, comments

It is slightly awkward to have "denies" array with each entry
having "deny" element which is numeric. let it be "bits"

"access" is also a possibility, but it is already used, and I would not
like to reuse, makes grepping harder, more ambiguity for the reader.
dca4d27b2c8c...
dca4d27b2c8c0cd5c7bbe3d8557715dd35d383ba
Sergei Petrunia
MDEV-24813: Signal full scan to storage engines.

Basic InnoDB Implementation.
Adds its own tests.
23 tests in innodb test suite fail.
da9ef7143277...
da9ef714327784c91d297269340a87f82799846d
Marko Mäkelä
fixup! 99959b558e7089f6611d0cadf0b58b8a608a79b3
d90406e8e71a...
d90406e8e71a071f1534f03d3a9ab6babfdbd497
Marko Mäkelä
fixup! 99959b558e7089f6611d0cadf0b58b8a608a79b3
d66580c71257...
d66580c71257cc5ce88432361921356d119a95e3
Dave Gosselin
MDEV-38921: Incorrect ORDER BY Result

Test to show the bug.
c84dfbd94d8c...
c84dfbd94d8cd21e473d416773e7cc3641fe488a
nada
MDEV-38624: disallow skipping ER_CONNECTION_KILLED

Prevent ER_CONNECTION_KILLED (1927) from being added to the slave_error_mask bitmap in init_slave_skip_errors(), even when explicitly listed in --slave-skip-errors or when using --slave-skip-errors=all. A warning is emitted in the error log when either is attempted.
c43bf13631f4...
c43bf13631f45e2c0a7a64b5da043af45af99c72
ParadoxV5
MDEV-38825 Slave delays when there is "nothing" to replicate

Delayed Replication does not delay on certain metadata events,
but not every type of “non-user” event.
GTID List and Binlog Checkpoint are two of them,
and because the primary sends them after a replica connects,
this replica delays upon START SLAVE even when it’s already up-to-date.

This commit fixes this oddity by changing this condition
set to check the entire non-group event category.
c408e5501acd...
c408e5501acdeae2ff0192ecd520384142bedcf5
Vladislav Vaintroub
more cleanup
c048d959ae7a...
c048d959ae7a3a608c0590c0947d8fdc97d8bb28
Vladislav Vaintroub
more cleanup
b98f295592d7...
b98f295592d7402cf71af8c9f73026df9621ee65
Oleg Smirnov
MDEV-38045: Implement QB_NAME hint with path syntax for nested query blocks

Extended QB_NAME hint to support path-based addressing of query blocks
nested within views, derived tables, and CTEs, following TiDB's syntax.

New syntax:
  QB_NAME(name, query_block_path), where
    query_block_path ::= query_block_path_element
                          [ {, query_block_path_element }... ]
    query_block_path_element ::= @ qb_path_element_select_num |
                                    qb_path_element_view_sel
    qb_path_element_view_sel ::= qb_path_element_view_name
                                  [ @ qb_path_element_select_num ]

For example,
  `SELECT /*+ qb_name(qb_v1, v1) */* FROM v1`
The name `qb_v1` is assigned to the inner query block of the view `v1`.

  `SELECT /*+ qb_name(qb_v1, v1@sel_1) */* FROM v1`
Means the same but specifies that `v1` is present in SELECT#1 of the current
query block.

  `SELECT /*+ qb_name(qb_v1, v1@sel_1 .@sel_2) */* FROM v1`
This means SELECT#2 of view `v1`, which is present in SELECT#1 of
the current query block, gets the name `qb_v1`.

It is possible to specify not only view names but also derived tables
and CTE's in the path.

Views and derived tables may be nested on multiple levels, for example:
  `SELECT /*+ qb_name(dt2_dt1_v1_1, dt1 .dt2 .v2 .@SEL_2)
              no_index(t1@dt2_dt1_v1_1)*/ v1.*
  FROM v1 JOIN (SELECT v1.* FROM v1 JOIN (SELECT * FROM v2) dt2) dt1`

Limitations:
  - Only SELECT statements support QB names with path. DML operations
    (UPDATE, DELETE, INSERT) only support explicitly defined QB names
b77cc3d691b1...
b77cc3d691b1f7ca3bfcb057735b8436863ac657
Dmitry Shulga
MDEV-30645: CREATE TRIGGER FOR { STARTUP | SHUTDOWN }

Core implementation

- Extended the sql grammar to support creation of system triggers
  on startup/shutdown
- System triggers metadata is loaded from the table mysql.event
- System triggers can be created only by users with the SUPER privilege
- Added the option --sys_triggers for mysqldump to dump system triggers.
  The option is turned off by default.
ad6c7acace29...
ad6c7acace295fca95ab4ed88764ba5bf84a3342
Marko Mäkelä
fixup! 99959b558e7089f6611d0cadf0b58b8a608a79b3

mtr_t::commit_file(): Ensure that log archive rotation will complete.

log_checkpoint_low(): Prevent duplicated fil_names_clear().
ac39602698e0...
ac39602698e0d2a40b84e837f3ce0436945b1f54
ParadoxV5
MDEV-38825 Slave delays when there is "nothing" to replicate

Delayed Replication does not delay on certain metadata events,
but not every type of “non-user” event.
GTID List and Binlog Checkpoint are two of them,
and because the primary sends them after a replica connects,
this replica delays upon START SLAVE even when it’s already up-to-date.

This commit fixes this oddity by changing this condition
set to check the entire non-group event category.
abef9ea9f6d7...
abef9ea9f6d7f9a6d1a0f1683b721712d03e740a
Yuchen Pei
MDEV-24813 Signal full scan to storage engines.

When starting to do a full table/index scan without a WHERE or JOIN
condition, tell the storage engine so and the corresponding LIMIT.

Include a do-nothing innodb implementation

(Comment and code edited by Sergei Petrunia)
a370860ce07c...
a370860ce07c7114ab9115bc21f8ba7f47aeb582
bsrikanth-mariadb
MDEV-38805:Store optimizer_context into a IS table

Currently, optimizer context is written as JSON sub-element in the
Optimizer Trace.

In this task, we separate it out from the optimizer trace, and instead
store it in optimizer_context Information Schema table.

The structure of the context is changed to look like below: -
----------------------------------
CREATE TABLE t1 ( ... );
-- in case it is a constant table
REPLACE INTO t1 VALUES (...);

CREATE TABLE t2 ( ... );
...

set @context='{ JSON with all the captured calls }';
set @optimizer_context='context';

... the original query;
----------------------------------

The IS can be used to read the current stored context, as well as to
dump it to a sql file which can later be replayed in a different
environment.

It is done like below: -
--------------------------------------
set optimizer_record_context=ON;
set optimizer_trace=1

-- sample query

select into outfile '/tmp/captured-context.sql' context from information_schema.OPTIMIZER_CONTEXT;
---------------------------------------

All the existing tests are modified to query OPTIMIZER_CONTEXT IS table
98e04ad8d7cf...
98e04ad8d7cf3bbef83b700bd9d6541f588b41bb
Vladislav Vaintroub
report error on REVOKE DENY, if the privilege is not currently denied.
96e35e35a389...
96e35e35a389d18b476cdaa533a7cef7b83a59f1
Yuchen Pei
MDEV-24813 Signal full scan to storage engines.

When starting to do a full table/index scan without a WHERE or JOIN
condition, tell the storage engine so and the corresponding LIMIT.

Include a do-nothing innodb implementation

(Comment and code edited by Sergei Petrunia)
7db944e23209...
7db944e23209acbb885ced089cf9d32a54b7cfab
Vladislav Vaintroub
x
7b54798a6ffc...
7b54798a6ffcf35d5b79c2ec2902a8ca3a1b2732
Dave Gosselin
MDEV-38649: Wrong result upon condition pushdown to table with DESC key

Initial test case that passes because bug is present.
79107c4a348a...
79107c4a348a6a80010cdb376355ddb918057a78
Marko Mäkelä
fixup! 99959b558e7089f6611d0cadf0b58b8a608a79b3
676cbea94a6c...
676cbea94a6c7ba63c8240d8c971bbc30d131f29
Daniel Black
MDEV-38913: pam_mariadb_mtr.so installation path change

This reverts the effect of MDEV-21654 and includes
pam_mariadb_mtr in the mariadb-test-data Deb package.

This allows our CI systems to run tests on the
pam implementation on Debian systems.

As the pam configuration can include a full path,
we've change the installation of the pam module
pam_mariadb_mtr.so to under the /usr/lib*/plugins/test_pam_modules
directory and configured the pam configuration file,
suite/plugins/pam/mariadb_mtr, to include the
full path to pam_mariadb_mtr.so.
57eacceff5f8...
57eacceff5f851cdf0b08bdf3cce388229468b58
Nikita Malyavin
MDEV-38840 optimize store_record/restore_record to use aligned copy

benchmarks.

To see the result in realistic load, run:
python run_mariadb_bench_inlined.py > results_final.plain
python convert_benchmarks.py
558af9e24e72...
558af9e24e7290918004d524c1d489245ccd8aac
Nikita Malyavin
MDEV-38840 optimize store_record/restore_record to use aligned copy

benchmarks.

To see the result in realistic load, run:
python run_mariadb_bench_inlined.py > results_final.plain
python convert_benchmarks.py
53eda9c8b02f...
53eda9c8b02f76b1430c2a832a93b4982bf65cdd
Alexander Barkov
MDEV-19635 System package SYS.DBMS_SQL

In progress
520fc4bffbd4...
520fc4bffbd40968e6dd3bf6dfd63440586ebb1c
Dave Gosselin
MDEV-38649: Wrong result upon condition pushdown on table with DESC key

QUICK_SELECT_DESC::get_next() sets a stale end range on the storage engine.
When checking the first range, it sets last_range to the first range and
then, if it cannot avoid descending scan, it sets the minimum endpoint on
the storage engine.  However, get_next() may decide that this range is not
a match after updating the minimum endpoint on the storage engine.  In this
case, it will continue to the next range.  When continuing, it needs to
reset not only the state of 'last_range' to point to the next range that
it's checking, but it also needs to clear the now-stale end range set on
the storage engine.  While this explanation covers the first and second
ranges, the issue at hand extends to the general case of ranges 1...N-1 and N.

Before this change and when get_next() decided that a range was not a match, it
would clear last_range at each loop continuation point.  Rather than clearing
the minimum endpoint on the storage engine at each continuation, we move all
loop cleanup to a lambda that's invoked by the for loop directly.  This
consolidates any logic that needs to be evaluated on loop continuation to one
place and reduces code duplication.

MySQL fixed this same problem at sha b65ca959efd6ec5369165b1849407318b4886634
with a different implementation.
4e7c4cf2ad75...
4e7c4cf2ad75f7a169f1dccba3f528a5322c7deb
Rex Johnston
MDEV-35333 Performance Issue on TPC-H Query 18

A patch illustrating how estimating the selectivity of a
grouping derived table with a having clause at 0.5 can have
a positive effect on the execution time of TPC-H Query#18
33ffc88db271...
33ffc88db2719df11fba8fdc75a109bc3a7244f9
bsrikanth-mariadb
MDEV-38805:Store optimizer_context into a IS table

Currently, optimizer context is written as JSON sub-element in the
Optimizer Trace.

In this task, we separate it out from the optimizer trace, and instead
store it in optimizer_context Information Schema table.

The structure of the context is changed to look like below: -
----------------------------------
CREATE TABLE t1 ( ... );
-- in case it is a constant table
REPLACE INTO t1 VALUES (...);

CREATE TABLE t2 ( ... );
...

set @context='{ JSON with all the captured calls }';
set @optimizer_context='context';

... the original query;
----------------------------------

The IS can be used to read the current stored context, as well as to
dump it to a sql file which can later be replayed in a different
environment.

It is done like below: -
--------------------------------------
set optimizer_record_context=ON;
set optimizer_trace=1

-- sample query

select into outfile '/tmp/captured-context.sql' context from information_schema.OPTIMIZER_CONTEXT;
---------------------------------------

All the existing tests are modified to query OPTIMIZER_CONTEXT IS table
30a82bb3733d...
30a82bb3733db3f94ceb10e2d9c15d22cb462e29
Oleg Smirnov
MDEV-38045: Implement QB_NAME hint with path syntax for nested query blocks

Extended QB_NAME hint to support path-based addressing of query blocks
nested within views, derived tables, and CTEs, following TiDB's syntax.

New syntax:
  QB_NAME(name, query_block_path), where
    query_block_path ::= query_block_path_element
                          [ {, query_block_path_element }... ]
    query_block_path_element ::= @ qb_path_element_select_num |
                                    qb_path_element_view_sel
    qb_path_element_view_sel ::= qb_path_element_view_name
                                  [ @ qb_path_element_select_num ]

For example,
  `SELECT /*+ qb_name(qb_v1, v1) */* FROM v1`
The name `qb_v1` is assigned to the inner query block of the view `v1`.

  `SELECT /*+ qb_name(qb_v1, v1@sel_1) */* FROM v1`
Means the same but specifies that `v1` is present in SELECT#1 of the current
query block.

  `SELECT /*+ qb_name(qb_v1, v1@sel_1 .@sel_2) */* FROM v1`
This means SELECT#2 of view `v1`, which is present in SELECT#1 of
the current query block, gets the name `qb_v1`.

It is possible to specify not only view names but also derived tables
and CTE's in the path.

Views and derived tables may be nested on multiple levels, for example:
  `SELECT /*+ qb_name(dt2_dt1_v1_1, dt1 .dt2 .v2 .@SEL_2)
              no_index(t1@dt2_dt1_v1_1)*/ v1.*
  FROM v1 JOIN (SELECT v1.* FROM v1 JOIN (SELECT * FROM v2) dt2) dt1`

Limitations:
  - Only SELECT statements support QB names with path. DML operations
    (UPDATE, DELETE, INSERT) only support explicitly defined QB names
29f2626e48d8...
29f2626e48d8d11431810c153e6ef390ce1e145e
Oleg Smirnov
MDEV-38045: Implement implicit query block names for optimizer hints

This patch implements support for implicit query block (QB) names in
optimizer hints, allowing hints to reference query blocks and tables
within derived tables, views and CTEs without requiring explicit
QB_NAME hints.

Examples.
-- Addressing a table inside a derived table using implicit QB name
select /*+ no_index(t1@dt) */ *
  from (select * from t1 where a > 10) as DT;
-- this is an equivalent to:
select /*+ no_index(t1@dt) */ * from
  (select /*+ qb_name(dt)*/ * from t1 where a > 10) as DT;
-- Addressing a query block corresponding to the derived table
select /*+ no_bnl(@dt) */ *
  from (select * from t1, t2 where t.1.a > t2.a) as DT;

-- View
create view v1 as select * from t1 where a > 10 and b > 100;
-- referencing a table inside a view by implicit QB name:
select /*+ index_merge(t1@v1 idx_a, idx_b) */ *
  from v1, t2 where v1.a = t2.a;
-- equivalent to:
create view v1 as select /*+ qb_name(qb_v1) */ *
  from t1 where a > 10 and b > 100;
select /*+ index_merge(t1@qb_v1 idx_a, idx_b) */ *
  from v1, t2 where v1.a = t2.a;

-- CTE
with aless100 as (select a from t1 where b <100)
  select /*+ index(t1@aless100) */ * from aless100;
-- equivalent to:
with aless100 as (select /*+ qb_name(aless100) */ a from t1 where b <100)
  select /*+ index(t1@aless100) */ * from aless100;

Limitations:
  - Only SELECT statements support implicit QB names. DML operations
    (UPDATE, DELETE, INSERT) only support explicit QB names
23f0615dd6c3...
23f0615dd6c33884470fda8b4486a120c5d61f06
Oleg Smirnov
MDEV-38045: Implement QB_NAME hint with path syntax for nested query blocks

Extended QB_NAME hint to support path-based addressing of query blocks
nested within views, derived tables, and CTEs, following TiDB's syntax.

New syntax:
  QB_NAME(name, query_block_path), where
    query_block_path ::= query_block_path_element
                          [ {, query_block_path_element }... ]
    query_block_path_element ::= @ qb_path_element_select_num |
                                    qb_path_element_view_sel
    qb_path_element_view_sel ::= qb_path_element_view_name
                                  [ @ qb_path_element_select_num ]

For example,
  `SELECT /*+ qb_name(qb_v1, v1) */* FROM v1`
The name `qb_v1` is assigned to the inner query block of the view `v1`.

  `SELECT /*+ qb_name(qb_v1, v1@sel_1) */* FROM v1`
Means the same but specifies that `v1` is present in SELECT#1 of the current
query block.

  `SELECT /*+ qb_name(qb_v1, v1@sel_1 .@sel_2) */* FROM v1`
This means SELECT#2 of view `v1`, which is present in SELECT#1 of
the current query block, gets the name `qb_v1`.

It is possible to specify not only view names but also derived tables
and CTE's in the path.

Views and derived tables may be nested on multiple levels, for example:
  `SELECT /*+ qb_name(dt2_dt1_v1_1, dt1 .dt2 .v2 .@SEL_2)
              no_index(t1@dt2_dt1_v1_1)*/ v1.*
  FROM v1 JOIN (SELECT v1.* FROM v1 JOIN (SELECT * FROM v2) dt2) dt1`

Limitations:
  - Only SELECT statements support QB names with path. DML operations
    (UPDATE, DELETE, INSERT) only support explicitly defined QB names
2306b430164e...
2306b430164e1eea86f03ad26486647488dd3a79
ParadoxV5
MDEV-38825 Slave delays when there is "nothing" to replicate

Delayed Replication does not delay on certain metadata events,
but not every type of “non-user” events.
GTID List and Binlog Checkpoint are two of them,
and because the primary sends them after a replica connects,
this replica delays upon START SLAVE even when it’s already up-to-date.

This commit fixes this oddity by changes this condition
set to check the entire non-group event category.
1fb571d80eb2...
1fb571d80eb2f05ad9c66c5f79166d97c5cbfbe9
Oleg Smirnov
MDEV-38045: Implement implicit query block names for optimizer hints

This patch implements support for implicit query block (QB) names in
optimizer hints, allowing hints to reference query blocks and tables
within derived tables, views and CTEs without requiring explicit
QB_NAME hints.

Examples.
-- Addressing a table inside a derived table using implicit QB name
select /*+ no_index(t1@dt) */ *
  from (select * from t1 where a > 10) as DT;
-- this is an equivalent to:
select /*+ no_index(t1@dt) */ * from
  (select /*+ qb_name(dt)*/ * from t1 where a > 10) as DT;
-- Addressing a query block corresponding to the derived table
select /*+ no_bnl(@dt) */ *
  from (select * from t1, t2 where t.1.a > t2.a) as DT;

-- View
create view v1 as select * from t1 where a > 10 and b > 100;
-- referencing a table inside a view by implicit QB name:
select /*+ index_merge(t1@v1 idx_a, idx_b) */ *
  from v1, t2 where v1.a = t2.a;
-- equivalent to:
create view v1 as select /*+ qb_name(qb_v1) */ *
  from t1 where a > 10 and b > 100;
select /*+ index_merge(t1@qb_v1 idx_a, idx_b) */ *
  from v1, t2 where v1.a = t2.a;

-- CTE
with aless100 as (select a from t1 where b <100)
  select /*+ index(t1@aless100) */ * from aless100;
-- equivalent to:
with aless100 as (select /*+ qb_name(aless100) */ a from t1 where b <100)
  select /*+ index(t1@aless100) */ * from aless100;

Limitations:
  - Only SELECT statements support implicit QB names. DML operations
    (UPDATE, DELETE, INSERT) only support explicit QB names
1a0d46af1771...
1a0d46af177127d591547b2305944d5a8a5528af
Raghunandan Bhat
MDEV-38864: Use mmap for MEMORY engine allocations

MEMORY engine blocks used to store data and indexes are allocated using
malloc/my_malloc. This created internal fragmentation within the system
allocator.

Switch to memory mapping for MEMORY engine's allocations.
0c90a2e344f3...
0c90a2e344f3281537d3d7328683e26e226d905a
Marko Mäkelä
fixup! e0f9da296be06feacb3fd1614ce7dd6ebde827e9
00d360d52af8...
00d360d52af8124dc6fe442898373918e91fc9d5
Marko Mäkelä
fixup! 99959b558e7089f6611d0cadf0b58b8a608a79b3

address trivial review comments
BuildBot (0.8.9) working for the MariaDB project.
Page built: Sat 28 Feb 2026 10:35:23 (UTC)