tokudb: alter table... drop primary key doesn't properly rename tablespace files

Bug #1671801 reported by Rick Pizzi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Invalid
Undecided
Unassigned
5.6
Opinion
Undecided
Unassigned
5.7
Opinion
Undecided
Unassigned

Bug Description

Please consider following table:

CREATE TABLE `BUG_DEMO` (
  `id` int(11) NOT NULL,
  `newcol` int(11) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=TokuDB DEFAULT CHARSET=latin1 ROW_FORMAT=TOKUDB_UNCOMPRESSED;

This is how tablespace files appear on filesystem:

[root@dbcache05 data]# ls -l _sbtest_BUG_DEMO_*
-rw-rw---- 1 mysql mysql 32768 Mar 10 13:07 _sbtest_BUG_DEMO_main_10db207cc_2_1d.tokudb
-rw-rw---- 1 mysql mysql 16384 Mar 10 13:07 _sbtest_BUG_DEMO_status_10db207cc_1_1d.tokudb

Now if we drop primary key via "alter table BUG_DEMO drop primary key", the tablespace files are left pointing to some temporary file names and are no longer easily identified:

-rw-rw---- 1 mysql mysql 32768 Mar 10 13:08 _sbtest_sql_3af4_38_main_10db21c8b_2_1d.tokudb
-rw-rw---- 1 mysql mysql 16384 Mar 10 13:08 _sbtest_sql_3af4_38_status_10db21c8b_1_1d.tokudb

Server version: 5.6.35-80.0-log

Tags: tokudb
Revision history for this message
George Ormond Lorch III (gl-az) wrote :

Tracking in https://jira.percona.com/browse/TDB-39, please login there to Percona JIRA and 'watch' for future updates. Marking it as opinion here as there is no other accurate matching state.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3660

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.