Pipeline Phase Visibility
PR #1000, contributed by @Shaurya2k06 in their first contribution. A pipeline that is still snapshotting behaves differently from one that has moved on to replication, and there was no way to tell them apart from the outside. The health server now exposes/status, reporting the current phase — snapshot or replication — and the same value is published as an OpenTelemetry gauge, so the transition can be alerted on:
/status is served alongside the existing /health and /ready endpoints by the run and snapshot commands.
Bug Fixes
- Snapshot requests with many tables no longer overflow the btree index (PR #1013). The unique index on snapshot requests included
table_namesdirectly; a request listing enough tables exceeded the btree entry size limit and could not be recorded. The column is hashed in the index instead, which bounds the entry regardless of how many tables a request names. - Custom enums are no longer reported as unsupported types (PR #1005). Preflight schema validation flagged user-defined enum columns as incompatible on sources that replicate them without trouble.
- Parsing of validated schema objects is deferred (PR #1003), by @tsg.
- A failed comment restore is a warning, not an error (PR #1009).
COMMENT ONstatements that fail during restore no longer abort it; a missing comment does not affect data or structure.
New Contributors
Upgrade
No configuration changes are required. Replace the binary and restart pgstream.Support
- Issues: https://github.com/xataio/pgstream/issues
- Documentation: https://github.com/xataio/pgstream/tree/main/docs
- Discussions: https://github.com/xataio/pgstream/discussions