Skip to main content
Use the @bijection/connectors/postgres entrypoint to declare PostgreSQL resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Database

cdc: cdc

The following example matches configuration standard.

Configuration: standard

Case: postgres/database/cdc/standard. Connection and resource configuration are declared by this exact case. Credential kind: postgres. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: lines
Collection: orders
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection owns host, port and database; the credential is a postgres credential (postgres.credential(name)). The tables of one database resource share one acquisition owner: one consistent initial snapshot, then committed transactions from logical replication, published atomically across the coupled tables. A lost replication history blocks acquisition rather than silently resuming. The PostgreSQL protocol is native; this connector declares tables and setup, and the engine owns replication, snapshot handoff and recovery.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.