pipework 0.243.0 → 0.246.0

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.246.0
+
+- **Added: covering indexes, `idx.index(name).on(...).include(...columns)` and the same on `idx.uniqueIndex`** (#879). The included columns are stored in the index snapshot and emitted as `INCLUDE (...)` after the key columns, so a lookup that reads only key and included columns can be an index-only scan. Adding, dropping or reordering included columns on an existing index migrates as an online replace (build `<name>_new` `CONCURRENTLY`, drop the old one `CONCURRENTLY`, rename). Indexes without `include` diff as before.
+
+## 0.245.0
+
+- **Added: a test about to time out says what its database connection is doing** (#874). At 2/3 of a test's timeout (its own `timeout`, else `testTimeout`), the harness writes one `pipework:test-watch` line (`console.warn`) naming the test; each backend on its test database(s) with state, wait event, seconds in state, `pg_blocking_pids` and the query (200 chars); and the host's `/proc/loadavg` and `/proc/pressure/{io,cpu}` where present. An `active` backend waiting on IO or a lock says Postgres or the disk stalled; `idle in transaction` on `ClientRead` says the test's own process did. It samples over its own short-lived admin connection, bounded at 5 s, and never fails or delays the test; a test that finishes first prints nothing. `TEST_WATCH_LOG_PREFIX` and `armTestWatch` are exported from `pipework/test`.
+- **Fixed: concurrent `alerts.raise` of one key could report a grouped raise as `resent` and queue a second delivery** (#875). Raises take their timestamp before waiting on the row lock, and "sent" was read from `last_sent_at = last_seen_at`, so two backends in the same microsecond tied. A raise now counts as sent only when its statement set `last_sent_at`, and `last_seen_at` never moves backwards.
+
+## 0.244.0
+
+- **Changed: a test process keeps its database across files instead of cloning and dropping one per file** (#870). The first file a vitest worker runs clones the template as before; when the file ends, the database is kept, and the next file in that worker gets it back reset to its state right after the clone: every table that grew is cleared, tables that had rows are reloaded, sequences restored. The reset checks a digest of the schema (tables, columns and types, constraints, indexes, policies, enums, partitions, functions and triggers, grants, database settings) and clones fresh instead when a file changed what a reset cannot undo (schema, settings, a prepared transaction, a refreshed materialized view); `pipework:test-reset` log lines name the reason. Reuse happens wherever a vitest worker process runs more than one file. Without a superuser the reload runs without `session_replication_role = replica`. **Opt out:** `test: { databasePerFile: true }` restores a clone and a queued drop per file.
+- **Changed: `docker-compose.test.yml` keeps the test cluster in memory and small** (#869): `wal_level=minimal` with `wal_skip_threshold=0` and `max_wal_senders=0` (no replication WAL; a table created in a transaction is not WAL-logged), `max_wal_size=256MB`, `checkpoint_timeout=30min`, `autovacuum=off`. Recreate the container to pick it up.
+
 ## 0.243.0
 
 - **Fixed: test setup failed with "No progress" while a long migration file was still applying** (#871). The template build reported progress only after each migration file committed, so a file whose statements together ran past `test.setupStallMs` on a loaded box (verity: 120+ s at `template-migrate`) failed the run. Setup now beats after every statement of a file (`template-migrate` detail `i/n <tag> stmt s/n`), before the first file (`start`, then `prepare <step>` for the tracker table, legacy tag recovery per file, the tag index and the applied read), and on each template-build step (`drop`, `create`, `owner`, `platform role`) and framework table statement. A single statement that hangs still trips the watchdog; its thresholds are unchanged. `applyMigrations` takes `onStatement(tag, statement, statements, index, total)` and `onPrepare(detail)`.