Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-252

PARTITION - Prune on Insert, Alter, Delete, Update

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    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

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          rspadim roberto spadim created issue -
          serg Sergei Golubchik added a comment -

          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.

          serg Sergei Golubchik added a comment - 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.
          rspadim roberto spadim added a comment -

          =) 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

          rspadim roberto spadim added a comment - =) 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
          rspadim roberto spadim added a comment -

          hi sergey, any information about mysql partition granular lock?

          rspadim roberto spadim added a comment - hi sergey, any information about mysql partition granular lock?
          serg Sergei Golubchik added a comment -

          not yet

          serg Sergei Golubchik added a comment - not yet
          rspadim roberto spadim made changes -
          Field Original Value New Value
          Summary PARTITION PRUNE ON INSERT AND ALTER OPERATIONS PARTITION - Prune on Insert, Alter, Delete, Update
          rspadim roberto spadim added a comment -

          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?

          rspadim roberto spadim added a comment - 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?
          rspadim roberto spadim added a comment -

          Waiting merge mysql 5.6 (5.6.6) to continue

          rspadim roberto spadim added a comment - Waiting merge mysql 5.6 (5.6.6) to continue
          rspadim roberto spadim made changes -
          rspadim roberto spadim added a comment -

          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

          rspadim roberto spadim added a comment - 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
          serg Sergei Golubchik made changes -
          Workflow defaullt [ 11651 ] MariaDB v2 [ 43041 ]
          serg Sergei Golubchik made changes -
          serg Sergei Golubchik made changes -
          ratzpo Rasmus Johansson (Inactive) made changes -
          Workflow MariaDB v2 [ 43041 ] MariaDB v3 [ 63900 ]
          serg Sergei Golubchik made changes -
          Priority Minor [ 4 ] Major [ 3 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 63900 ] MariaDB v4 [ 130058 ]

          People

            Unassigned Unassigned
            rspadim roberto spadim
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.