@yawlabs/postgres-mcp 0.11.0 → 0.11.1

package/CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.11.1] - 2026-08-23
+
+### Fixed
+- **Windows: the launcher no longer hard-kills the server on the first Ctrl-C.** There are no POSIX signals on Windows — `child.kill(sig)` ignores the name and calls `TerminateProcess`, an immediate hard kill (verified: a child with a `SIGTERM` handler never runs it and dies with `code=null`). The launcher forwarded anyway, on the stated assumption that this was a "no-op on Windows", so it aborted the graceful shutdown the console's own Ctrl-C had just started and skipped the server's `process.on("exit")` cleanup. The console already delivers the event to the whole process group, so on Windows the launcher now forwards nothing.
+- **A wedged server no longer leaves the launcher hanging.** Forwarding was gated on `child.killed`, which records only that `kill()` was *called* — never that the child is gone — so every signal after the first was swallowed and there was no escape hatch. Escalation is now armed by a timer on the first signal: one press is enough, and a child still alive after a 2s grace window is killed. Using a timer rather than counting signals also stops the ordinary supervisor sequence (`SIGINT` then `SIGTERM` milliseconds apart) from being misread as impatience.
+
+### Documentation
+
+- **The README now carries a "What's new in 0.11.0" section.** The three
+  breaking changes lived only in this file, where someone upgrading from
+  0.10.x is unlikely to look before their first failing call -- and the
+  stats-envelope change fails at the call site rather than at install time,
+  since `data` becomes an object where it used to be an array.
+- **Both WSL scripts and the README document the `MSYS_NO_PATHCONV=1` prefix
+  they require when invoked from Git Bash on Windows.** Without it, Git Bash
+  rewrites the `/mnt/c/...` argument into the Git install prefix before
+  `wsl.exe` sees it, and the script exits "No such file or directory" having
+  run no tests at all. Piping either script into `tail`/`head` is also called
+  out, because the pipeline's exit status is the last command's -- so a red
+  matrix reports success.
+
 ## [0.11.0] - 2026-08-23
 
 ### Added

package/README.md

@@ -11,6 +11,23 @@ Built and maintained by [Yaw Labs](https://yaw.sh).
 
 One click adds this to your local Yaw MCP config so it's available in every Yaw Terminal session. Or install manually below.
 
+## What's new in 0.11.0
+
+PostgreSQL 18 support, a new I/O observability tool, and version-gated catalog queries. Full detail in the [CHANGELOG](CHANGELOG.md).
+
+**Three breaking changes if you are upgrading from 0.10.x:**
+
+1. **`pg_seq_scan_tables`, `pg_unused_indexes` and `pg_top_queries` return an envelope, not a bare row array.** Read `data.rows` where you used to read `data`. The envelope carries `stats_reset`, because a cumulative scan count means nothing without knowing when the counters were last reset -- if that happened an hour ago, every index looks unused, which is how a load-bearing index gets dropped.
+2. **`pg_explain` with `analyze: true` now emits `BUFFERS`**, matching what PostgreSQL 18 does server-side. Plans get longer; pass `buffers: false` for the old output.
+3. **Node 22 is the floor.** Node 20 reached end of life.
+
+**Worth knowing even if you are not upgrading yet:**
+
+- `pg_describe_table` now flags generated and identity columns. Previously a generated column's expression surfaced as `default_value` with nothing marking it, so an agent read the column as optional-with-a-default and wrote an `INSERT` that PostgreSQL rejects.
+- New `pg_io_stats` exposes `pg_stat_io` (PG16+) plus in-flight async I/O from `pg_aios` and the active `io_method` (PG18+).
+- `pg_advisor` checks multixact wraparound alongside transaction-ID wraparound. A lock-heavy workload can exhaust multixacts while `relfrozenxid` still looks healthy.
+- Every version-dependent column is gated on `server_version_num`, so older servers get a thinner answer rather than an error.
+
 ## Backstory
 
 Anthropic's reference Postgres MCP server, `@modelcontextprotocol/server-postgres`, was [archived in May 2025](https://github.com/modelcontextprotocol/servers-archived/tree/main/src/postgres) and [marked deprecated on npm](https://www.npmjs.com/package/@modelcontextprotocol/server-postgres) in July 2025. Anthropic has not shipped a replacement. Despite the deprecation, the last published version (v0.6.2) is still pulled ~20,000 times per week - a lot of agents are pointed at an unmaintained package.

package/bin/postgres-mcp.mjs

@@ -268,16 +268,51 @@ if (mode === "node") {
       void runInProcess();
     });
 
-    // Forward termination so the server's own SIGINT/SIGTERM cleanup (pool
-    // drain) runs in the child instead of the child being orphaned. Signals
-    // are a no-op on Windows but harmless to register.
+    // Forward termination so the server's own shutdown path runs in the child
+    // rather than the child being orphaned.
+    //
+    // Registering ANY handler for these suppresses Node's default
+    // terminate-on-signal, so the parent's exit has to be arranged explicitly.
+    // `child.killed` only records that kill() was CALLED, never that the child
+    // is gone, so gating on it swallows every signal after the first and wedges
+    // the launcher with no escape hatch.
+    //
+    // Escalation is driven by a TIMER, not by counting signals. Counting is
+    // ambiguous: a supervisor routinely sends SIGINT then SIGTERM milliseconds
+    // apart, and a terminal Ctrl-C reaches the whole process group, so reading
+    // "a second signal" as impatience hard-kills a child that is already
+    // shutting down cleanly. A timer makes the count irrelevant -- ONE press is
+    // enough, and a wedged child dies on schedule. setTimeout is monotonic, so
+    // a wall-clock step cannot mis-gate the window either.
+    //
+    // POSIX vs Windows, and why we do NOT forward on Windows.
+    // On POSIX child.kill(sig) delivers a real, catchable signal, so forwarding
+    // is what lets the child run its shutdown. On Windows there are no POSIX
+    // signals: child.kill IGNORES the name and calls TerminateProcess -- an
+    // immediate hard kill (verified: a child with a SIGTERM handler never runs
+    // it and dies with code=null, signal=SIGTERM). Forwarding there ABORTS the
+    // graceful shutdown the console's own Ctrl-C just started, skipping the
+    // child's process.on("exit") cleanup. The console has already notified the
+    // child, so on Windows the timer below is the only kill we issue.
+    const ESCALATE_AFTER_MS = 2000;
+    let escalation = null;
     for (const sig of ["SIGINT", "SIGTERM"]) {
       process.on(sig, () => {
-        if (!child.killed) child.kill(sig);
+        // No try/catch: kill() on an already-exited child returns false, it does
+        // not throw. It throws only for a signal the platform does not know,
+        // which SIGINT/SIGTERM/SIGKILL never are.
+        if (!isWin) child.kill(sig);
+        if (escalation) return; // already counting down; further signals are noise
+        escalation = setTimeout(() => {
+          // Still here after its grace window. Stop waiting on it.
+          child.kill("SIGKILL");
+          process.exit(128 + (constants.signals[sig] ?? 15));
+        }, ESCALATE_AFTER_MS);
       });
     }
 
     child.on("exit", (code, signal) => {
+      if (escalation) clearTimeout(escalation);
       // Mirror the child's fate: a signal death becomes 128+n so callers see a
       // conventional shell exit status rather than a bare 0.
       if (signal) {

package/dist/index.js

@@ -39017,7 +39017,7 @@ function compareVersions(a, b) {
 }
 
 // src/index.ts
-var version2 = true ? "0.11.0" : await readPackageVersion();
+var version2 = true ? "0.11.1" : await readPackageVersion();
 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.11.0",
+  "version": "0.11.1",
   "mcpName": "io.github.YawLabs/postgres-mcp",
   "description": "PostgreSQL MCP server - query, schema introspection, explain, and health checks for AI assistants",
   "license": "MIT",