[MDEV-3932] 5.6 merge Created: 2012-12-11  Updated: 2013-08-17  Resolved: 2013-08-14

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: 10.0.4

Type: Task Priority: Blocker
Reporter: Sergei Golubchik Assignee: Unassigned
Resolution: Fixed Votes: 2
Labels: None

Issue Links:
Blocks
blocks MDEV-252 PARTITION - Prune on Insert, Alter, D... Open
blocks MDEV-3821 Server crashes in fetch_data_into_cac... Closed
blocks MDEV-4057 Mariadb default for performance_schem... Closed
blocks MDEV-4115 Merge InnoDB fulltext index from MySQ... Closed
blocks MDEV-4285 Server crashes in ptr_compare on NOW ... Closed
blocks MDEV-4288 DDL: crash after uninitialized read i... Closed
blocks MDEV-4615 PARTITION - Vertical Partitioning (us... Closed
blocks MDEV-4676 QUERY CACHE - partition lock prune an... Open
blocks MDEV-4721 Circular References Cause MariaDB 10.... Closed
blocks MDEV-4722 regression - update statement hangs s... Closed
blocks MDEV-4744 InnoDB Fulltext indexes Closed
PartOf
includes MDEV-3933 online alter table Closed
includes MDEV-4750 join_outer_innodb.test fails in 10.0-... Closed
includes MDEV-4751 Tracking test failures in 10.0-monty Closed
includes MDEV-4753 partition_innodb_stmt reports memory ... Closed
includes MDEV-4756 10.0-monty tree: log_state.test fails Closed
includes MDEV-4757 Change mysql.slow_log.event_time from... Closed
includes MDEV-4758 10.0-monty tree: ALTER TABLE CHANGE C... Closed
includes MDEV-4786 merge 10.0-monty → 10.0 Closed
Relates
relates to MDEV-4801 Server crashes in my_strdup on settin... Closed
relates to MDEV-4807 Assertion: trx->start_file != 0 fails... Closed
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
MDEV-3933 online alter table Technical task Closed Michael Widenius  
MDEV-4716 merge 5.6->10.0 Technical task Closed Oleksandr Byelkin  

 Description   

merge with the latest 5.6

 Comments   
Comment by roberto spadim [ 2013-07-08 ]

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!

Generated at Thu Feb 08 06:52:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.