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
f9f92b480e46...
f9f92b480e46e52453f2428509d55c38b1d01155
Marko Mäkelä
Merge 10.6 into 10.11
f780629e9426...
f780629e94264e306f5c12b03b486e18c45104ff
Monty
Remove rows and cost from optimizer trace for not usable key parts
  • winx64-debug: compile failed -  stdio
  • winx64-packages: compile failed -  stdio
f0b2e76577a1...
f0b2e76577a1b94d28671a3b6c53f08bce704821
Monty
Removed ctrl-l from the source
f06060f5ed3f...
f06060f5ed3f293763e034c011da6c6cf42ae3d5
Marko Mäkelä
Cleanup: Remove the function dict_remove_db_name()
d9bb2d0764d9...
d9bb2d0764d9c1582af3688090ff98d23453a520
Sergei Petrunia
MDEV-34894: Poor query plan, because range estimates are not reused for ref(const)

(Variant 4, with @@optimizer_adjust_secondary_key_costs, reuse in two
places, and conditions are replaced with equivalent simpler forms in two more)

In best_access_path(), ReuseRangeEstimateForRef-3,  the check
for whether
"all used key_part_i used key_part_i=const"
was incorrect: it may produced a "NO" answer for cases when we
had:
key_part1= const // some key parts are usable
key_part2= value_not_in_join_prefix  //present but unusable
key_part3= non_const_value // unusable due to gap in key parts.

This caused the optimizer to fail to apply ReuseRangeEstimateForRef
heuristics. The consequence is poor query plan choice when the index
in question has very skewed data distribution.

The fix is enabled if its @@optimizer_adjust_secondary_key_costs flag
is set.
d5a669b6b645...
d5a669b6b645926360c2a36a99d14501fe8c91fa
Julius Goryavsky
Merge branch '10.5' into '10.6'
cbc3c99df224...
cbc3c99df22433fde2da677a2573ee5d0394bb42
Monty
Optimized max_part_bit in sql_select.cc to use my_find_first_bit.
c8d040938a7e...
c8d040938a7ebe10e62506a726702c5990ef4dda
Sergei Petrunia
MDEV-34720: Poor plan choice for large JOIN with ORDER BY and small LIMIT

(Variant 2b: call greedy_search() twice, correct handling for limited
search_depth)

Modify the join optimizer to specifically try to produce join orders that
can short-cut their execution for ORDER BY..LIMIT clause.

The optimization is controlled by @@optimizer_join_limit_pref_ratio.
Default value 0 means don't construct short-cutting join orders.
Other value means construct short-cutting join order, and prefer it only
if it promises speedup of more than #value times.

In Optimizer Trace, look for these names:
* join_limit_shortcut_is_applicable
* join_limit_shortcut_plan_search
* join_limit_shortcut_choice
c8ce9fbb98b8...
c8ce9fbb98b82a3955f235f6b17077be85ad33f4
Oleg Smirnov
MDEV-33281 Make BNL() hint work for join_cache_level=0

join_cache_level=0 disables join cache buffers, but the hint
BNL() now allows to employ BNL(H) buffers for particular tables
or query blocks.

This commit also adds a number of test cases including
OUTER JOINs to make sure hints do not break the rules of
join buffers application
c41ab95a3899...
c41ab95a3899248059abe952725781fac32b51bf
Monty
Remove rows and cost from optimizer trace for not usable key parts
becc77bc1f34...
becc77bc1f341e7342eea69be29afaa5132b85d4
Yuchen Pei
MDEV-34716 [to-squash] 11.6 fixup caused by MDEV-31340

To be squashed with the top MDEV-34716 commit
bd64fdc0b984...
bd64fdc0b984649c78e9a52e583d23994102aea2
Thirunarayanan Balathandayuthapani
MDEV-34855 Bootstrap hangs while shrinking the system tablespace

Reason:
=======
- During bootstrap, InnoDB shrinks the system tablespace while purge is
still active on system tablespace. This could lead to deadlock.

Fix:
====
Avoid System tablespace shrinking during bootstrap.
Move the shrinking logic of system tablespace after purge gets shutdown.
bd616a3733c0...
bd616a3733c05a4f2854b4b390681a08c48dfe23
Nikita Malyavin
Auth: set thd->scramble in all cases during writing Initial Handshake Packet
bbbb429a1eb5...
bbbb429a1eb5d8e66b987d25a2d92614e755561d
Nikita Malyavin
Auth: release the plugins from responsibility to fill scramble_buff.

Fill it once during the Initial Handshake Packet parsing. This uses the fact
that the server guarantees first 20 bytes to be the scramble.
b0a1d953778f...
b0a1d953778fa50edebe2119e8faaf085c8f6a32
Vladislav Vaintroub
Fix threading issue during mariadb-import abort.
  • kvm-debug-asan-ubsan: uploading var.tar.gz -  
a340445c83c8...
a340445c83c8f8020c367b264802c34b5fab6318
Vladislav Vaintroub
Fix test case
9f0b106631f3...
9f0b106631f34da376e518a23c902b0f7fa26667
Marko Mäkelä
MDEV-34845 buf_flush_buffer_pool(): Assertion `!os_aio_pending_reads()' failed

buf_flush_buffer_pool(): Wait for any pending asynchronous reads
to complete. This assertion failed in a run where buf_read_ahead_linear()
had been triggered in an SQL statement that was executed right
before shutdown.

Reviewed by: Debarun Banerjee
9878238f7457...
9878238f7457280f3368e5d31b66aac49433c792
Marko Mäkelä
MDEV-34791: Redundant page lookups hurt performance

btr_cur_t::search_leaf(): When the index root page is also a leaf page,
we may need to upgrade our existing shared root page latch into an
exclusive latch. Even if we end up waiting, the root page won't be able
to go away while we hold an index()->lock. The index page may be split;
that is all.

btr_latch_prev(): Acquire the page latch while holding a buffer-fix
and an index tree latch. Merge the change buffer if needed. Use
buf_pool_t::page_fix() for this special case instead of complicating
buf_page_get_low() and buf_page_get_gen().

row_merge_read_clustered_index(): Remove some code that does not seem
to be useful. No difference was observed with regard to removing this
code when a CREATE INDEX or OPTIMIZE TABLE statement was run concurrently
with sysbench oltp_update_index --tables=1 --table_size=1000 --threads=16.

buf_pool_t::unzip(): Decompress a ROW_FORMAT=COMPRESSED page.

buf_pool_t::page_fix(): Handle also ROW_FORMAT=COMPRESSED pages
as well as change buffer merge. Optionally return an error.
Add a flag for suppressing a page latch wait and a special return
value -1 to indicate that the call would block.
This is the preferred way of buffer-fixing blocks.
The functions buf_page_get_gen() and buf_page_get_low() are only being
invoked with rw_latch=RW_NO_LATCH in operations on SPATIAL INDEX.

buf_page_t: Define some static functions for interpreting state().

buf_page_get_zip(), buf_read_page(),
buf_read_ahead_random(), buf_read_ahead_linear():
Remove the redundant parameter zip_size. We must look up the
tablespace and can invoke fil_space_t::zip_size() on it.

buf_page_get_low(): Require mtr!=nullptr.

buf_page_get_gen(): Implement some lock downgrading during recovery.

ibuf_page_low(): Use buf_pool_t::page_fix() in a debug check.
We do wait for a page read here, because otherwise a debug assertion in
buf_page_get_low() in the test innodb.ibuf_delete could occasionally fail.

PageConverter::operator(): Invoke buf_pool_t::page_fix() in order
to possibly evict a block. This allows us to remove some
special case code from buf_page_get_low().
98340531fff3...
98340531fff321a41a31575d9f36c9af310ee195
Marko Mäkelä
Merge 10.6 into 10.11
982bf06d560c...
982bf06d560c0266d3be0693c7f3d74c2689530e
Nikita Malyavin
MDEV-12320 configurable default authentication plugin for the server

* Add a new cmdline-only variable "default_auth_plugin".
* A default plugin is locked at the server init and unlocked at the deinit
  stages. This means that mysql_native_password and old_password_plugin, when
  default, are locked/unlocked twice.
90dbedb6200b...
90dbedb6200b179feb982077e8adddd3de9a9059
Dmitry Shulga
MDEV-34551: Column list in the trigger definition

Added support of the clause `update of <columns>` by the parser
and initial implementation of UPDATE statement processing.
8f072dd2e805...
8f072dd2e805bfee6b5bbeac3ff782fdb7473c56
Dmitry Shulga
MDEV-34551: Column list in the trigger definition

Added support of the clause `UPDATE OF <columns>` for
BEFORE/AFTER UPDATE triggers. Triggers defined with this clause
are fired and run actions only in case an UPDATE statement affects
any of the listed columns. For columns not specified in the clause
`UPDATE OF <columns>`, an UPDATE statement with such columns as
targets don't result in running a trigger.

Output of SHOW TRIGGERS doesn't affected by this task. Output of
the statement SHOW CREATE TRIGGER shows the clause `UPDATE OF <columns>`
if it was specified on trigger creation.
886d740ad770...
886d740ad77013d6d080c2907b632c817c9784c9
Monty
Optimized max_part_bit in sql_select.cc to use my_find_first_bit.
819765a47dd1...
819765a47dd1aab58fc1693ce7b19c1f3015b375
Sergei Petrunia
Code cleanup in test_if_skip_sort_order()

Added comments
Moved a part into find_indexes_matching_order().
7f2815f0c9d1...
7f2815f0c9d1db5b2e0fdcb22ccdf1635e8b7e8e
Monty
Remove rows and cost from optimizer trace for not usable key parts
6fd79fdd491a...
6fd79fdd491af6ab7f5a524249aaf22a1e7d37d6
Monty
Temp push of
TODO-4858: Make ref(const) access reuse estimates from range if possible
4e2c02a12c11...
4e2c02a12c1120501ab591f923cf9e624f688035
Denis Protivensky
MDEV-33133: MDL conflict handling code should skip BF-aborted trxs

It's possible that MDL conflict handling code is called more
than once for a transaction when:
- it holds more than one conflicting MDL lock
- reschedule_waiters() is executed,
which results in repeated attempts to BF-abort already aborted
transaction.
In such situations, it might be that BF-aborting logic sees
a partially rolled back transaction and erroneously decides
on future actions for such a transaction.

The specific situation tested and fixed is when a SR transaction
applied in the node gets BF-aborted by a started TOI operation.
It's then caught with the server transaction already rolled back,
but with no MDL locks yet released. This caused wrong state
detection for such a transaction during repeated MDL conflict
handling code execution.

Signed-off-by: Julius Goryavsky <[email protected]>
485b0248fbb8...
485b0248fbb848de667fa4a15b6b480fde933796
Julius Goryavsky
MDEV-30822: Adjust wsrep_sst_mariabackup.sh to understand both pre-MDEV-18931 and post-MDEV-18931 file naming

This commit adds support for legacy names for files such
as mariadb_backup_galera_info, mariadb_backup_checkpoints
and mariabackup_binlog_info to allow upgrading from old
to new server versions without stopping the galera cluster.

In addition, improved handling of errors to prevent hangs
detected during stress testing of the updated SST script
for mariabackup (when conditions for hangs at the mariabackup
stage were artificially created).
3d91bbdc271a...
3d91bbdc271ada347dec460523138ab1b8d1356f
Vladislav Vaintroub
Fix init_tp_connections
2ed33f2fb660...
2ed33f2fb660617aa39d4abb7e7383764e63ac8c
Ian Gilfillan
MDEV-26114: Update Sys Schema README
2da4839bb676...
2da4839bb6761c5c9164f76373ba82255bb18273
Marko Mäkelä
Merge 10.6 into 10.11
235f33e3606b...
235f33e3606b79c5e3b75f4cfd1ca6d92320e9a2
Denis Protivensky
MDEV-33133: MDL conflict handling code should skip BF-aborted trxs

It's possible that MDL conflict handling code is called more
than once for a transaction when:
- it holds more than one conflicting MDL lock
- reschedule_waiters() is executed,
which results in repeated attempts to BF-abort already aborted
transaction.
In such situations, it might be that BF-aborting logic sees
a partially rolled back transaction and erroneously decides
on future actions for such a transaction.

The specific situation tested and fixed is when a SR transaction
applied in the node gets BF-aborted by a started TOI operation.
It's then caught with the server transaction already rolled back,
but with no MDL locks yet released. This caused wrong state
detection for such a transaction during repeated MDL conflict
handling code execution.

Signed-off-by: Julius Goryavsky <[email protected]>
1c438cdbf923...
1c438cdbf923c702b58aa66b1b76c918592d10fa
Yuchen Pei
MDEV-15696 Implement SHOW CREATE SERVER

One change is that if the port is not supplied or out of bound, the
old behaviour is to print 3306. The new behaviour is to not print
it (if not supplied) or the out of bound value.
13b3f20fd01b...
13b3f20fd01bb7a3af643b4ed3aed0976beba855
Monty
Optimized max_part_bit in sql_select.cc to use my_find_first_bit.
  • winx64-debug: compile failed -  stdio
  • winx64-packages: compile failed -  stdio
134f159a00ef...
134f159a00efdb4ec8f72f3d5e1a5e72bb99b25f
Vladislav Vaintroub
WIP
12d781870616...
12d781870616a03b7c0ec446b95a07c31dea7305
Nikita Malyavin
Auth: release the plugins from responsibility to fill scramble_buff.

Fill it once during the Initial Handshake Packet parsing. This uses the fact
that the server guarantees first 20 bytes to be the scramble.
05e8a97cb253...
05e8a97cb253a1d21e454babe166e916df4dcf84
Vladislav Vaintroub
mariadb-import, multithreading - improve error handing

In case of error in one connection, issue KILL CONNECTION for all others,
or server will still do LOAD FILE, possibly for hours, after we exited.
024a18dbcb7f...
024a18dbcb7f9c44094db03daa013fd8ba3c58b7
Marko Mäkelä
MDEV-34823 Invalid arguments in ib_push_warning()

In the bug report MDEV-32817 it occurred that the function
row_mysql_get_table_status() is outputting a fil_space_t*
as if it were a numeric tablespace identifier.

ib_push_warning(): Remove. Let us invoke push_warning_printf() directly.

innodb_decryption_failed(): Report a decryption failure and set the
dict_table_t::file_unreadable flag. This code was being duplicated in
very many places. We return the constant value DB_DECRYPTION_FAILED
in order to avoid code duplication in the callers and to allow tail calls.

innodb_fk_error(): Report a FOREIGN KEY error.

dict_foreign_def_get(), dict_foreign_def_get_fields(): Remove.
This code was being used in dict_create_add_foreign_to_dictionary()
in an apparently uncovered code path. That ib_push_warning() call
would pass the integer i+1 instead of a pointer to NUL terminated
string ("%s"), and therefore the call should have resulted in a crash.

dict_print_info_on_foreign_key_in_create_format(),
innobase_quote_identifier(): Add const qualifiers.

row_mysql_get_table_error(): Replaces row_mysql_get_table_status().
Display no message on DB_CORRUPTION; it should be properly reported at
the SQL layer anyway.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Sun 08 Sep 2024 01:59:24 (UTC)