Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

Post 8.0 GA Triage Work

General

Escalation

General

Escalation

Description

If you see something that is deferred from 8.0 GA but should be considered at the top of the list for tasks once GA ships, link the issue to this one using a "relates to" link.

Environment

None

Linked issues

is blocked by

[PS8QA] handle_fatal_signal (sig=8) in std::_Hashtable | /opt/rh/devtoolset-7/root/usr/include/c++/7/bits/hashtable.h:1421

[PS8QA] handle_fatal_signal (sig=6) in compression_dict::cols_table_delete_low | sql/sql_zip_dict.cc:765

Re-Implement Utility User Feature in PS 8.0

TokuDB can't be installed on cosmic due to libjemalloc missing

relates to

Research if our SUPER-requiring features should start requiring dynamic privileges

[PS8QA] compression dictionary operations not handled under innodb-force-recovery

Add missing 8.0.13 testcases

Fix missing lock binlog for backup for TokuBackup

[PS8QA] Assertion `innodb_trx_id == 0 || innodb_trx_id == trx_id || is_attachable_transaction_active()' failed.

[PS8QA] Assertion `m_protocol->type() == Protocol::PROTOCOL_TEXT || m_protocol->type() == Protocol::PROTOCOL_BINARY' failed.

[PS8QA] Assertion `MDL_checker::i s_read_locked(m_thd, *object)' failed.

[PS8QA] handle_fatal_signal (sig=11) in handler::get_ha_share_ptr

[PS8QA] Assertion `!drop_ctx->has_tmp_trans_tables()' failed in rm_table_eval_gtid_and_table_groups_state(THD*, Drop_tables_ctx*)

query returns incorrect result for table with no PK and non-unique CHAR utf8mb4 SK

mysql.service gets masked when upgrading from upstream

conflict happens on the innochecksum when PS 8 is installed over upstream on Debian/Ubuntu

Can't upgrade with encrypted undo tablespaces from 5.7.24 to 8.0.13

"Tmp_table_sizes: 0" in extended slow query log while temp tables are present

Broken fields in user statistics

[PS8QA] Assertion `innodb_trx_id == 0 || innodb_trx_id == trx_id || is_attachable_transaction_active()' failed.

Dropping a trigger from a TokuDB table that contains non-ascii characters could lead to a crash

native_part::Partition_base::<...> -> handler::ha_open -> __cxa_pure_virtual () -> ABORT

MyRocks altering a column/table comment rebuilds a table

UBSAN sql/log_event.cc:8652:22: runtime error: load of value 190, which is not a valid value for type 'bool'

Hide compression dictionary tables from information_schema.innodb_tables

Test LOCK TABLES FOR BACKUP with performance_schema.log_status and LOCK INSTANCE FOR BACKUP

TokuDB partitioning and empty sql_mode could lead to a crash on a debug build

Smart Checklist

Activity

Show:

Won't Do

Details

Assignee

Unassigned

Reporter

Peter Schwaller(Deactivated)

Time tracking

4m logged

Priority

Medium

Epic Name

Post 8.0 GA Work

Smart Checklist

Created December 13, 2018 at 12:38 PM

Updated February 7, 2025 at 8:38 AM

Resolved February 7, 2025 at 8:38 AM