james.maesandClaude Opus 5.5
f8d25d1f7c
Query plan record action and POST explain: plain or generic EXPLAIN, and EXPLAIN (ANALYZE, BUFFERS) for single SELECTs in a rolled-back READ ONLY transaction with statement_timeout, behind explain_analyze, always audited, ANALYZE plans and parameters never stored. UI API extension /qqq/v1/qbit/db-performance (overview, activity with live text only for view_live_text, explain, statements/lookup) with a committed OpenAPI fragment and contract test. Eight full-width typed home widgets. Data-driven help bundle with a coverage test. README, CHANGELOG and UPGRADE. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.4 KiB
Upgrading QBit DB Performance
First release
There is no previous published release. See CHANGELOG.md for additions and README.md for complete installation.
Use QQQ 4.1.0-RC.11 or newer, Java 21, and PostgreSQL 13 or newer (16+ for generic plans). Include db/liquibase/qbit-db-performance/db_performance.changelog.sql once in your application's Liquibase changelog. Run migrations through the host deployment before collecting statistics; the qbit does not apply them automatically.
Preload and create pg_stat_statements, then grant pg_read_all_stats to the application's database role through your normal provisioning. Without the role the collector reports reduced visibility. Preserve existing rule and settings edits; seeding is insert-only.
Register the producer and a host scheduler. Grant db_performance.view and the narrower operator permissions appropriate to each role; ANALYZE and raw live text require separate grants. Existing deployments using an early scaffold's db_perf.* grants must use the actual db_performance.* names (or the configured permission base).
Collect twice to establish useful deltas. Inspect Setup for access and schedule status. UI hosts need the optional qqq-middleware-javalin dependency so the four endpoints register in the standard UI API. The help bundle version is filtered from the Maven project version during the build.