physical replication
Keep a standby aligned with the primary’s physical database changes.
Use this when You need a compatible whole-database standby for read offload or recovery.
without the term
“Keep a compatible standby using the database’s storage changes and verify safe promotion.”
with the term · How do you ask a model for physical replication?
Verify physical replication prerequisites, WAL retention, replay lag, and a fenced standby-promotion drill.
What is physical replication?
Physical replication transfers storage-level changes. PostgreSQL streaming replication sends WAL records for a compatible standby to replay; it differs from publishing selected logical table changes.
Why does physical replication matter when vibe coding?
An agent can assume any database version or subset of tables can use the same physical replay stream.
How do you do physical replication?
Check version and storage compatibility, base backup, retained WAL, and replay lag. Drill promotion and prevent the old primary from remaining writable.
What goes wrong with physical replication?
A lagging standby can lose acknowledged asynchronous writes on failover. Replication does not replace independently retained backups.
Sources for this entry
- PostgreSQL: Log-shipping standby servers
Primary/standby streaming replication, asynchronous lag, and synchronous acknowledgement configurations.
- PostgreSQL: Failover
Promotion, client routing, preventing the old primary from continuing as a writer, and restoring redundancy.
Sources checked . Source checks do not establish human editorial approval. How we check content.