mirror of
https://github.com/MariaDB/server.git
synced 2026-01-21 19:04:52 +01:00
b2f6216695
This bug happens when using galera, max_tmp_session_space_usage and a transaction that uses temporary file of a size between 'binlog-cache-size' (default 32K) and 64K followed by a change user command. In the case of a transaction of size between 32k and 64k, the server don't truncate the binary log file on disk to speed up things, which is fine. The bug was that change_user() reset the tmp_space_used variable and the next time the temporary_file was truncated, we got a negative value for tmp_space_used, which caused the error "Local temporary space limit reached". Fixed by not resetting tmp_space_used in init(), which is called by change_user(). Other things - Truncate binary log cache files when change_user() is called. This makes the new users session not depending on log file sizes by previous user. - Some new ASSERT and DBUG_ENTER - Fixed typo in DBUG output in ma_pagecache.c |
||
|---|---|---|
| .. | ||
| archive | ||
| atomic | ||
| binlog | ||
| binlog_encryption | ||
| client | ||
| compat | ||
| csv | ||
| encryption | ||
| engines | ||
| events | ||
| federated | ||
| funcs_1 | ||
| funcs_2 | ||
| galera | ||
| galera_3nodes | ||
| galera_3nodes_sr | ||
| galera_sr | ||
| gcol | ||
| handler | ||
| heap | ||
| innodb | ||
| innodb_fts | ||
| innodb_gis | ||
| innodb_i_s | ||
| innodb_zip | ||
| jp | ||
| json | ||
| large_tests | ||
| maria | ||
| mariabackup | ||
| merge | ||
| mtr/t | ||
| mtr2 | ||
| multi_source | ||
| optimizer_unfixed_bugs | ||
| parts | ||
| perfschema | ||
| perfschema_stress | ||
| period | ||
| plugins | ||
| roles | ||
| rpl | ||
| s3 | ||
| sql_sequence | ||
| storage_engine | ||
| stress | ||
| sys_vars | ||
| sysschema | ||
| unit | ||
| vcol | ||
| versioning | ||
| wsrep | ||