Skip to content

docs: update SHOW STORAGE INFO global/per-DB split and SHOW LICENSE INFO#1655

Merged
vpavicic merged 5 commits into
release/3.11from
show_info_update
Jun 16, 2026
Merged

docs: update SHOW STORAGE INFO global/per-DB split and SHOW LICENSE INFO#1655
vpavicic merged 5 commits into
release/3.11from
show_info_update

Conversation

@andrejtonev

@andrejtonev andrejtonev commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Release note

Reflect show_storage_info_disk_fix changes:

  • Rewrite bare SHOW STORAGE INFO to instance-only schema; add breaking-change callout (field renames + global_isolation_level/global_storage_mode now report startup defaults).
  • Document SHOW STORAGE INFO ON CURRENT DATABASE and correct enterprise gating (non-default DB only).
  • Add memory_limit_policy row + evaluation matrix to SHOW LICENSE INFO.
  • Add ShowStorageInfo global metric to monitoring.
  • Fix stale field references across storage-memory-usage, transactions, vector-search, enabling-memgraph-enterprise, backup-and-restore, and migration pages.

Related product PRs

PRs from product repo this doc page is related to:
memgraph/memgraph#4155

Checklist:

  • Add appropriate milestone (current release cycle)
  • Add bugfix or feature label, based on the product PR type you're documenting
  • Make sure all relevant tech details are documented
  • Check all content with Grammarly
  • Perform a self-review of my code
  • The build passes locally
  • My changes generate no new warnings or errors

Reflect show_storage_info_disk_fix changes:
- Rewrite bare SHOW STORAGE INFO to instance-only schema; add breaking-change
  callout (field renames + global_isolation_level/global_storage_mode now report
  startup defaults).
- Document SHOW STORAGE INFO ON CURRENT DATABASE and correct enterprise gating
  (non-default DB only).
- Add memory_limit_policy row + evaluation matrix to SHOW LICENSE INFO.
- Add ShowStorageInfo global metric to monitoring.
- Fix stale field references across storage-memory-usage, transactions,
  vector-search, enabling-memgraph-enterprise, backup-and-restore, and migration
  pages.
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview, Comment Jun 15, 2026 2:15pm

Request Review

- faq: bare SHOW STORAGE INFO is instance-level only; node/relationship
  counts moved to the per-database variant.
- tenant-profiles: only non-default DB requires Enterprise; default DB and
  ON CURRENT DATABASE work on all editions.
- release-notes: note Community-edition support for ON DATABASE <default> /
  ON CURRENT DATABASE.
…y subset

The per-database tables in storage-memory-usage and tenant-profiles list
only the memory-related fields; point readers to the complete 15-field set
in server-stats and stop implying the memory subset is the full output.
Only SHOW STORAGE INFO ON CURRENT DATABASE is new in 3.11; ON DATABASE
<name> (#3952) and SHOW MEMORY INFO predate it. Reword the lead-in and
point to the availability note for the per-query edition/privilege split.
@andrejtonev andrejtonev added status: ready PR is ready for review feature Documentation related to a new product feature of feature update labels Jun 15, 2026
@andrejtonev andrejtonev added this to the 3.11 milestone Jun 15, 2026
…SE INFO

The license memory limit gates (license.cpp): AI_PLATFORM limits the
graph_memory_tracker (graph + query, the query+graph_memory_tracked arena),
not "graph only"; ENTERPRISE limits total memory (graph + query + vector
index). Align the License types table with memory_limit_policy, server-stats,
and vector-search. Also fix the --memory-limit anchor.
@vpavicic vpavicic merged commit 54d475b into release/3.11 Jun 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Documentation related to a new product feature of feature update status: ready PR is ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants