[katarinasupe]

Description

Documents SHOW SESSIONS and TERMINATE SESSIONS on the Transactions page and in the query privileges table. Also fixes two older statements on the same page: TERMINATE TRANSACTIONS $id (parameters were never accepted) and the new database column of SHOW TRANSACTIONS (memgraph/memgraph#4571).

Not done:

• SHOW ACTIVE USERS also gained columns in #4571 (server-stats page).
• #4577's release note says SESSIONS is now a reserved keyword; on the daily build sessions still works as a variable name, so the docs don't mention it.
• The snapshot phase values come back lowercase ("vertices"), while the table on the page lists them in uppercase (older text, not changed here).

Checked on the 20261011 daily build (c829e614, includes #4577, #4571 and #4843): SHOW SESSIONS columns, TERMINATE SESSIONS results and errors, parameters, explicit transactions, terminating idle and running sessions, and both SHOW TRANSACTIONS outputs (snapshot rows show the database too). Enterprise privilege rules not run.

Related: #1831 documents memgraph/memgraph#4843.

Product PR

memgraph/memgraph#4577

Checklist

• For a product change: milestone set to the release and feature or bugfix label added
• For a product change: this PR is linked from the product PR's documentation checklist

[vercel]

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

Project	Deployment	Actions	Updated
documentation	Ready	Preview	Oct 20, 2026 11:55am UTC

[andrejtonev]

Thanks for writing this up! I checked every statement against current master (6e9c79da3), on a live instance as well as in the code. Most of it is accurate. The inline comments cover two statements that are wrong for 3.14 (SESSIONS isn't reserved, and the forced-DROP DATABASE example no longer applies after #4843), a few that overstate what happens (killed: true, "running query is aborted"), and some behaviour that's missing: open-transaction rollback, what the client sees and driver retries, auth disabled, Community vs Enterprise, impersonation, coordinators, LOGOFF and $id parameters. Every suggestion was re-run against master.

Three things outside this diff:

1. TERMINATE TRANSACTIONS $id (around line 340): "A parameterized id is treated exactly like a literal one, so running TERMINATE TRANSACTIONS $id with $id = "*" also terminates everything." This has never worked. The grammar only accepts a literal there (transactionId : literal, unchanged since the query was added), so TERMINATE TRANSACTIONS $id is a syntax error (extraneous input '$' expecting ...) whatever $id is. The sentence came in with v3.13 (#1689). Suggested replacement: "Transaction ids, including "*", must be string literals. Query parameters such as $id aren't supported and cause a syntax error."
2. SHOW TRANSACTIONS columns (line 95): since memgraph#4571 (3.14, listed under breaking changes in #1764), SHOW TRANSACTIONS returns an 8th column, database, after elapsed_ms. The page still says "contains seven columns", and the column table and example outputs don't include it. Suggested row: | database | String | The database the transaction is running on. |
3. PR description: it says the SHOW TRANSACTIONS fix is internal and "the release note already covers it". It doesn't: on release/3.14 the only #4577 entry is the feature line. I've suggested a bug-fix line on #1764.

[katarinasupe]

@andrejtonev this PR is updated based on #1831. Can you take a look at this PR again and approve if it's fine. Also, feel free to review the other PR as well. Thank you!

[andrejtonev]

Thanks, the 10-12 commits cover almost all of the first round: the reserved-keyword sentence, FORCE, $id, coordinators, LOGOFF, impersonation, Community and the termination outcomes are all in, and they hold on 3.14.0-rc3. A few things are left inline: the idle-client sentence (a plain query fails once before the driver reconnects), the database column of SHOW SESSIONS, and three small ones.

Outside this diff:

• #1843 and #1844 also edit transactions.mdx. Git merges all three cleanly in either order. #1843 rewrites the walkthrough just above ## Manage sessions (base lines 434-440), so this PR's hunk context there (the old infinite query message) is stale on GitHub, but that's only cosmetic. Two dependencies to keep in mind when merging:
  • #1843's snapshot and GC db_name rows say "The database column shows the same value", but the database row of the column table is added here. #1843 alone points at a column the table doesn't list.
  • This PR leaves two 7-column outputs (the GC example and the walkthrough); #1843 replaces both. The PR body's "phase values … uppercase (older text, not changed here)" is also fixed by #1843. Merging the two together, or this one first, avoids an in-between state.
• Wording shared with #1843 (SHOW ACTIVE USERS INFO). The login timestamp and impersonation wording match. The database column doesn't (inline N2): #1843 gives the main-database fallback but not "", this PR gives "" but not the fallback. Both columns return the same value, so both pages should say both.
• #1844 (LOGOFF clears session state). No contradiction. On re-login as another user the session keeps its session_id, and username and database change to the new login's. See inline N6.
• Release notes. #1845 removes "SESSIONS is a reserved keyword" from the 3.14 notes. There's still no bug-fix line for the SHOW TRANSACTIONS / SHOW ACTIVE USERS INFO foreign-read race (memgraph/memgraph#4571, memgraph/memgraph#4577).