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

Atomic DROP DATABASE

    XMLWordPrintable

Details

    Description

      All DDL operations must be atomic before we can really claim to support Atomic DDL (MDEV-17567).

      DROP DATABASE was only made crash-safe in MDEV-24408; it is not atomic yet. With the following approach, it should become atomic on XA-capable storage engines:

      An atomic implementation of DROP DATABASE would involve the following internal steps:

      1. XA START
      2. For each table in storage engines, invoke handler::delete_table().
      3. If everything succeeded, invoke handlerton::drop_database in each storage engine that implements it.
      4. XA PREPARE in each storage engine
      5. XA COMMIT or XA ROLLBACK in each storage engine.

      Attachments

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. MDEV-4259 transactional DDL

          • Major - Major loss of function.
          • Open
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-25919 InnoDB reports misleading lock wait timeout on DDL operations

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-17567 Atomic DDL

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

          Task - A task that needs to be done. MDEV-24408 Crash-safe DROP DATABASE

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

          Activity

            People

              monty Michael Widenius
              marko Marko Mäkelä
              Votes:
              1 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.