You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONFIGURATION.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,16 +94,16 @@ The schema ships with a small, query-driven set of indexes. The most important o
94
94
Run the read-only benchmark against your own database to confirm the planner is using the expected indexes and to record baseline latencies:
95
95
96
96
```sh
97
-
npm run db:benchmark
98
-
npm run db:benchmark -- --runs 5 --kind 1 --limit 500
97
+
pnpm db:benchmark
98
+
pnpm db:benchmark --runs 5 --kind 1 --limit 500
99
99
```
100
100
101
101
The `db:benchmark` script loads the local `.env` file automatically (via `node --env-file-if-exists=.env`), using the same `DB_HOST`/`DB_PORT`/`DB_USER`/`DB_PASSWORD`/`DB_NAME` variables as the relay. The benchmark issues only `EXPLAIN (ANALYZE, BUFFERS)` and `SELECT` statements — it never writes. Flags: `--runs <n>` (default 3), `--kind <n>` (default 1 / `TEXT_NOTE`; pass `0` for SET_METADATA), `--limit <n>` (default 500), `--horizon-days <n>` (default 7), `--help`.
102
102
103
103
For a full before/after proof of the index impact (seeds a throwaway dataset, drops and recreates the indexes, and prints a BEFORE/AFTER table), use:
104
104
105
105
```sh
106
-
npm run db:verify-index-impact
106
+
pnpm db:verify-index-impact
107
107
```
108
108
109
109
The hot-path index migration (`20260420_120000_add_hot_path_indexes.js`) uses `CREATE INDEX CONCURRENTLY`, so it can be applied to a running relay without taking `ACCESS EXCLUSIVE` locks on the `events` or `invoices` tables.
0 commit comments