Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Splitted from MDEV-29583. There are many tickets (see related tickets) that may have been caused by self-referencing (e.g. t1 -> t2 -> t3 -> t1) or multi-referencing (e.g. t1 -> t <- t2) spider tables. Verify whether self-/multi- referencing is indeed the cause.
Attachments
Issue Links
- relates to
-
MDEV-29605 SIGSEGV in spider_db_ping on INSERT
- Confirmed
-
MDEV-29606 Assertion `transaction->implicit_xid.is_null()' failed in THD::init_for_queries and Assertion `transaction.is_empty()' failed in prepare_new_connection_state
- Confirmed
-
MDEV-29676 Dual thread hang in 'closing tables' and 'Waiting for table metadata lock' on Spider CREATE OR REPLACE TABLE
- Closed
-
MDEV-29854 SIGSEGV in spider_string::length on LOCK TABLES
- Closed
-
MDEV-30011 SIGSEGV in spider_db_mbase::fin_loop_check on I_S SELECT
- Open
-
MDEV-30012 Triple thread hang in states 'NULL', 'NULL' and 'closing tables' on INSERT
- Open
- split from
-
MDEV-29583 Disallow Spider self/dual/multi/cross-referencing tables, consider not executing/skipping/disabling init_connect for Spider user
- Closed