Details
-
Task
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
None
Description
merge with the latest 5.6
Attachments
Issue Links
- blocks
-
MDEV-252 PARTITION - Prune on Insert, Alter, Delete, Update
-
- Open
-
-
MDEV-3821 Server crashes in fetch_data_into_cache_low on concurrent select from I_S and ALTER TABLE
-
- Closed
-
-
MDEV-4057 Mariadb default for performance_schema differs from MySQL 5.6.x
-
- Closed
-
-
MDEV-4115 Merge InnoDB fulltext index from MySQL 5.6
-
- Closed
-
-
MDEV-4285 Server crashes in ptr_compare on NOW and CAST in ORDER BY
-
- Closed
-
-
MDEV-4288 DDL: crash after uninitialized read in row_merge_buf_add
-
- Closed
-
-
MDEV-4615 PARTITION - Vertical Partitioning (using spider engine)
-
- Closed
-
-
MDEV-4676 QUERY CACHE - partition lock prune and invalidation query cache
-
- Open
-
-
MDEV-4721 Circular References Cause MariaDB 10.x to Lock Up
-
- Closed
-
-
MDEV-4722 regression - update statement hangs server on MariaDB 10.0.3
-
- Closed
-
-
MDEV-4744 InnoDB Fulltext indexes
-
- Closed
-
- includes
-
MDEV-3933 online alter table
-
- Closed
-
-
MDEV-4750 join_outer_innodb.test fails in 10.0-monty
-
- Closed
-
-
MDEV-4751 Tracking test failures in 10.0-monty
-
- Closed
-
-
MDEV-4753 partition_innodb_stmt reports memory leaks from dict/dict0stats_bg.cc:69
-
- Closed
-
-
MDEV-4756 10.0-monty tree: log_state.test fails
-
- Closed
-
-
MDEV-4757 Change mysql.slow_log.event_time from TIMESTAMP to TIMESTAMP(6).
-
- Closed
-
-
MDEV-4758 10.0-monty tree: ALTER TABLE CHANGE COLUMN doesn't drop EITS stats
-
- Closed
-
-
MDEV-4786 merge 10.0-monty → 10.0
-
- Closed
-
- relates to
-
MDEV-4801 Server crashes in my_strdup on setting innodb_ft_user_stopword_table to DEFAULT
-
- Closed
-
-
MDEV-4807 Assertion: trx->start_file != 0 fails in trx0trx.cc on killing CREATE TABLE query
-
- Closed
-
1.
|
online alter table |
![]() |
Closed | Michael Widenius |
2.
|
merge 5.6->10.0 |
![]() |
Closed | Oleksandr Byelkin |
Hi guys, i know that i'm not a big voice here in mariadb, i'm just a user and a begginer in mariadb/mysql source code
but... while executing the merge of partition locks, think about how to send this information (partitions used) to query cache, today we only cache 'table' information, not the partitions used in that table
maybe should be nice mark parts of code where query cache partition information should be set/retrieved, and after 5.6 merge, implement a query cache prune over partitions, i'm talkin about this MDEV-4676
Thanks guys, good work! you are amazing!