Details

    • Type: Task
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Fix Version/s: 10.0.4
    • Component/s: None
    • Labels:
      None

      Description

      merge with the latest 5.6

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Hide
              rspadim roberto spadim added a comment -

              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!

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

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  serg Sergei Golubchik
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Time Spent - 1 week, 3 days, 5 hours Remaining Estimate - 1 week, 2 days
                    1w 2d
                    Logged:
                    Time Spent - 1 week, 3 days, 5 hours Remaining Estimate - 1 week, 2 days
                    1w 3d 5h