@yawlabs/postgres-mcp 0.6.11 → 0.6.12

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.12] - 2026-05-16
+
+### Fixed
+- `pg_inspect_locks` now resolves `relation` for the common case of row-level
+  contention. Previously, `SELECT FOR UPDATE` + `UPDATE` row-level waits
+  queued on a `transactionid` lock with `pg_locks.relation = NULL`, so the
+  handler returned `relation: null` and gave the agent no hint as to which
+  table was contested. A fallback subquery now resolves the contested table
+  from the blocker's held write-intent relation locks (RowShareLock,
+  RowExclusiveLock, etc.), filtering out plain SELECT's AccessShareLock so
+  unrelated tables the blocker only read from don't show up. Closes #5.
+
 ## [0.6.11] - 2026-05-16
 
 ### Infrastructure

package/dist/index.js

@@ -36391,7 +36391,35 @@ var adminTools = [
                      FROM pg_catalog.pg_class c
                      JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
                      WHERE c.oid = bl.relation)
-             ELSE NULL
+             ELSE (
+               -- transactionid / virtualxid waits have bl.relation = NULL
+               -- because the wait is on the blocker's xid, not on a relation.
+               -- The contested table is usually identifiable from the
+               -- blocker's held write-intent locks: SELECT FOR UPDATE takes
+               -- RowShareLock, UPDATE/INSERT/DELETE take RowExclusiveLock,
+               -- migrations take stronger modes. Filter out the AccessShare
+               -- locks (plain SELECT) the blocker also holds on every table
+               -- they read from -- those aren't the contention source. If
+               -- the blocker has touched multiple write-intent tables in
+               -- their transaction, this is a best-effort hint, not a
+               -- definitive answer; the blocked/blocking queries above let
+               -- the caller disambiguate.
+               SELECT n.nspname || '.' || c.relname
+               FROM pg_catalog.pg_locks blocker_locks
+               JOIN pg_catalog.pg_class c ON c.oid = blocker_locks.relation
+               JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
+               WHERE blocker_locks.pid = blocking.pid
+                 AND blocker_locks.locktype = 'relation'
+                 AND blocker_locks.granted
+                 AND blocker_locks.mode IN (
+                   'RowShareLock', 'RowExclusiveLock', 'ShareLock',
+                   'ShareRowExclusiveLock', 'ShareUpdateExclusiveLock',
+                   'ExclusiveLock', 'AccessExclusiveLock'
+                 )
+                 AND n.nspname NOT IN ('pg_catalog', 'information_schema')
+               ORDER BY n.nspname, c.relname
+               LIMIT 1
+             )
            END AS relation,
            bl.locktype AS lock_type
          FROM pg_catalog.pg_locks bl
@@ -37550,7 +37578,7 @@ function compareVersions(a, b) {
 }
 
 // src/index.ts
-var version2 = true ? "0.6.11" : (await null).createRequire(import.meta.url)("../package.json").version;
+var version2 = true ? "0.6.12" : (await null).createRequire(import.meta.url)("../package.json").version;
 var subcommand = process.argv[2];
 if (subcommand === "version" || subcommand === "--version") {
   console.log(version2);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yawlabs/postgres-mcp",
-  "version": "0.6.11",
+  "version": "0.6.12",
   "mcpName": "io.github.YawLabs/postgres-mcp",
   "description": "PostgreSQL MCP server - query, schema introspection, explain, and health checks for AI assistants",
   "license": "MIT",