[MDEV-252] PARTITION - Prune on Insert, Alter, Delete, Update Created: 2012-05-04  Updated: 2015-06-10

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: roberto spadim Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: None

Issue Links:
Blocks
is blocked by MDEV-3932 5.6 merge Closed

 Description   

Hi again
well last year i was testing partition prune and i checked that a insert isn´t pruned since i executed a partition alter table on a partition X and inserted a row at partition Y, and the result was a insert lock until alter table end...
the bug/feature request was reported at mysql team, but i don´t know why they don´t accept more feature requests just bugs (maybe a oracle principle of only enterprise clients)

check:
http://bugs.mysql.com/bug.php?id=60190

could be nice to have a lock per partition and not per table, there´s a problem since .frm file is a file to all partitions and a lock of a partition may lock this file, and this get back to a lock of table and not a partition lock

well i think at bug sent to mysql is better explained
thanks

 Comments   
Comment by Sergei Golubchik [ 2012-05-16 ]

There is an ongoing work (in MySQL) on more granular locks for partitioned tables (basically, to be able to lock individual partitions, not a table as a whole). If it is implemented in MySQL, we will merge it from upstream in a due time.

Comment by roberto spadim [ 2012-05-16 ]

=) nice, no problem, i think it's will be a good tool, since in futures we can implement diferent partitions /tables type (mariadb+innodb for example) and others stuff, like alter a partition with some index and the other partition with anothers index, this is very useful for history partitions (no index) and 'today' partitions ideas/uses

well let's wait

Comment by roberto spadim [ 2013-06-05 ]

hi sergey, any information about mysql partition granular lock?

Comment by Sergei Golubchik [ 2013-06-05 ]

not yet

Comment by roberto spadim [ 2013-06-18 ]

hi sergei, maybe this is done in mysql...
http://dev.mysql.com/doc/refman/5.6/en/partitioning-limitations-locking.html
MySQL 5.6.6 implements partition lock pruning, which eliminates unneeded locks in many cases. In MySQL 5.6.6 and later, most statements reading from or updating a partitioned MyISAM table cause only the effected partitions to be locked.

this is very usefull, could we support it too?

Comment by roberto spadim [ 2013-06-18 ]

Waiting merge mysql 5.6 (5.6.6) to continue

Comment by roberto spadim [ 2013-06-18 ]

found the worklog of mysql:
http://dev.mysql.com/worklog/task/?id=4443
and bug report in bug system
http://bugs.mysql.com/bug.php?id=37252

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