PostgreSQL
PostgreSQL is the source of your change data capture pipeline.
AvailabilityAvailable to everyone with early access to Varqeni.
How it works
- Setup: a read-only role that can read replication slot and write-ahead log state, the publication, and the heartbeat table. Fortis sets it up with you.
- What it reads: whether the slot is active, how much write-ahead log it holds, how much is unconfirmed, and how old the last heartbeat is.
- What it cannot do: change data, drop or move a slot, or change a publication. Those are never automated.
What you should see: The PostgreSQL part of the pipeline diagram, and Heartbeat age and WAL held by slot at the top of the Overview.
What it can and cannot do
Can
- Read slot, write-ahead log, publication and heartbeat state on self-managed PostgreSQL through a read-only role.
Cannot
- Change data or slots, or connect to managed cloud PostgreSQL such as Amazon RDS or Aurora yet.
Related articles
- Read PostgreSQL healthVarqeni watches the PostgreSQL server itself, not only the replication slot a pipeline uses: transactions held open, slots nobody reads and connections in use.
- Debezium on Kafka ConnectVarqeni reads connector and task state, and can resume a paused connector or restart a failed task within your rules.
- What Varqeni reads, and what it does notVarqeni reads the state of your pipeline, never the rows of your data.
- What is plannedIntegrations on the way, none of which are available today.
Still stuck? Contact support or email info@fortisdatagroup.com.