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

reintroduce delete_while_scanning to multi_delete

Details

    • Task
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 11.8.1
    • Parser
    • None

    Description

      For MDEV-30469, I removed delete_while_scanning as the implementation now gathers row ids and defers deletes to send_eof. However, we can reintroduce delete_while_scanning for the case when neither ORDER BY...LIMIT nor hints are present.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35848 Multi-table DELETE with order by...limit works incorrect

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is caused by

          New Feature - A new feature of the product, which has yet to be developed. MDEV-30469 Support ORDER BY and LIMIT for multi-table DELETE, index hints for single-table DELETE.

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Dave Gosselin made transition -
            Open In Progress
            		7d 3h 5m 1
            Dave Gosselin made transition -
            In Progress In Review
            		2d 5h 15m 1
            Oleksandr Byelkin made transition -
            In Review Stalled
            		25d 16h 38m 1
            Dave Gosselin made transition -
            Stalled Closed
            		4h 32m 1

            People

              Gosselin Dave Gosselin
              Gosselin Dave Gosselin
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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