[MCOL-3464] mysqld crash with no default schema Created: 2019-08-28  Updated: 2021-04-19  Resolved: 2020-09-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: 1.2.5
Fix Version/s: 5.4.1

Type: Bug Priority: Critical
Reporter: David Hill (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2020-7, 2020-8

 Description   

Customer report issue with mysqld crashing when they ran a query when now default schema was provided. Support was able to reproduce the crash by creating the same tables the customer had along with a 'view'.

From customer

Aug 28 10:02:59 usfit-scdb1 kernel: mysqld[126996]: segfault at 0 ip 00007f279d032149 sp 00007f276c5a9bf0 error 4 in libcalmysql.so.1.0.0[7f279cf8d000+127000]
Aug 28 10:03:01 usfit-scdb1 kernel: mysqld[127091]: segfault at 0 ip 00007f3e67157149 sp 00007f3e38177bf0 error 4 in libcalmysql.so.1.0.0[7f3e670b2000+127000]
Aug 28 10:03:01 usfit-scdb1 kernel: mysqld[127091]: segfault at 0 ip 00007f3e67157149 sp 00007f3e38177bf0 error 4 in libcalmysql.so.1.0.0[7f3e670b2000+127000]

I was able to reproduce on a single server system. Customers is a 2um 2pm system.



 Comments   
Comment by David Hill (Inactive) [ 2020-02-26 ]

Customer reported BUG still happened in 1.4.2 release. Which is probably expected

Comment by Daniel Lee (Inactive) [ 2020-09-15 ]

Build verified: 1.5.4-1 (drone #631), 1.4.5-1 (drone #600)

Reproduced the issue in 1.5.3-1

Generated at Thu Feb 08 02:42:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.