Status (CLI)

SQL: status() / stats(). The CLI adds read-only checks of the host installation, cluster settings and the heartbeat.

sudo postvec doctor --database app --deep
sudo postvec doctor --database app --deep --format json \
  | jq '{summary, failures: [.checks[] | select(.status == "FAIL")]}'

Flag	Effect
--deep	Heartbeat must advance; hash CLI-installed model receipts
--strict	Warnings fail the command
--format json	Versioned object on stdout; progress on stderr

doctor is read-only: host files, cluster settings and the heartbeat.

Expected

Exit 0. JSON summary has no FAIL checks. If doctor (or the worker log) asks for ALTER EXTENSION, the library and installed SQL disagree: upgrade.

Inside a container, use postvec-healthcheck or an explicit socket URL. See Docker.

docker exec postvec postvec-healthcheck
docker exec -u postgres postvec \
  postvec doctor \
  --database-url 'postgresql:///app?host=/var/run/postgresql' \
  --database app --deep

On postvec-server:

postvec-server status
curl -sk https://127.0.0.1:22222/ready

status prints the binary version, the resident models, and every member of the cluster with its address, status and version. /ready answers 200 once a model can serve, and 503 with a reason before the first model loads and during a drain.

See status (SQL) for column queues and worker counters, and troubleshooting for the symptom table.