[MDEV-30580] Investigate whether self-/multi- referencing spider tables cause problems Created: 2023-02-06  Updated: 2023-02-06

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - Spider
Fix Version/s: None

Type: Task Priority: Major
Reporter: Yuchen Pei Assignee: Yuchen Pei
Resolution: Unresolved Votes: 1
Labels: None

Issue Links:
Issue split
split from MDEV-29583 Disallow Spider self/dual/multi/cross... Closed
Relates
relates to MDEV-29605 SIGSEGV in spider_db_ping on INSERT Confirmed
relates to MDEV-29606 Assertion `transaction->implicit_xid.... Confirmed
relates to MDEV-29676 Dual thread hang in 'closing tables' ... Closed
relates to MDEV-29854 SIGSEGV in spider_string::length on ... Closed
relates to MDEV-30011 SIGSEGV in spider_db_mbase::fin_loop_... Open
relates to MDEV-30012 Triple thread hang in states 'NULL', ... Open

 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.
Generated at Thu Feb 08 10:17:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.