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

Materialized Views: DML (design + dev + review)

    XMLWordPrintable

Details

    Description

      Read-path / transaction integration for MDEV-12163 — Materialized Views.

      Scope (design + dev + code review together):

      • THD::LOMV (list of materialised views used by current transaction) data structure + lifecycle.
      • Table open path: in TDC, detect 'this is a materialised view'; check LOMV; either reuse the already-pinned TABLE_SHARE (so the transaction keeps reading a consistent version) or open the latest version and add a record / bump refcount in the registry.
      • Same path under LOCK TABLES (open once at lock time; refcount adjusted at UNLOCK TABLES).
      • Transaction end: walk LOMV, unlink each, decrement refcount; if it drops to 0 and a newer version exists, drop the now-obsolete versioned table and remove its registry record.
      • Visibility guarantee: a long-running transaction continues reading the version it pinned, while new transactions see the latest version immediately.
      • Code-review iteration.

      Depends on: MDEV-12163's REFRESH VIEW side ticket (storage layout + registry).

      Estimate baseline: ~11d (design + dev + code review combined).

      Attachments

        Activity

          People

            shulga Dmitry Shulga
            julien.fritsch Julien Fritsch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - 11d
                11d
                Remaining:
                Remaining Estimate - 11d
                11d
                Logged:
                Time Spent - Not Specified
                Not Specified

                Git Integration

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