Skip to content

3.6.0

Latest
Latest

Choose a tag to compare

View all tags
@erikdarlingdata erikdarlingdata released this 27 Aug 11:16
v3.6.0
4bb851a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Darling and Lite 3.6.0 — UAT release.

Store schema v79 → v104 (25 migration rungs; the full upgrade path was verified end to end against a real v3.5.0 store — climbed to v104, matched the constant, re-ran idempotent). An existing store upgrades on first start; no action required.

PostgreSQL parity — the bulk of this release

  • Configuration and its history — get_pg_server_config (non-default first, with source and whether a change needs a restart) and get_pg_server_config_changes, plus a Configuration tab. Names pending_restart loudly, the state where the file and the running server disagree.
  • Deadlocks with the whole graph — read from the server log: the wait edges, the victim, and every participant's full statement. Needs nothing configured on the target.
  • All four trend reads — wait, query-duration, I/O and database-stats over time, so "is this getting worse" finally has a PostgreSQL answer.
  • PostgreSQL 18 support — measured byte totals from the reshaped pg_stat_io, and the major-version persistence that lets a read explain a column its version removed.
  • Multi-role store exposure — postgres.network.role accepts admin and viewer at once, one hostssl rule per role.

Also

  • Ten PostgreSQL MCP tools that shipped unreachable are now registered, with a reflection pin so it can't recur.
  • Opt-in GCF output format for MCP results (external contribution) — 29.7% fewer tokens on real payloads.
  • Azure SQL DB deadlock telemetry and database-size sibling rows; Lite collection-reset race fixed.

On PostgreSQL plan capture

Ships as built and tested to the limit the fleet allows: proven end to end on a self-hosted target (real plans captured, stored, read back), the RDS transport's parse pinned against real captured bytes, its AWS calls covered by faked-client tests. The one hop not demonstrated is a plan travelling out of a live Aurora log blob — loading auto_explain there needs a parameter-group change and reboot. pg_plan_capture_readiness reports the outstanding prerequisites on any managed target that has them.

Full detail in CHANGELOG.md under this version.

Assets 17
Loading