Functionality | Oracle | PostgreSQL |
---|---|---|
A standby server that can accept connections and serves read-only queries | Active Data Guard | Hot Standby |
A standby server that cannot be connected to until it is promoted to a master server | Physical Standby Server | Warm Standby |
A data-modifying transaction is not considered committed until all servers have committed the transaction. | Maximum Availability | Synchronous |
Allow some delay between the time of a commit and its propagation to the other servers. Some transactions might be lost in the switch to a backup server load balanced servers might return slightly stale results. |
Maximum Performance | Asynchronous |
Do not allow any transactions to be unprotected at any time | Maximum Protection |
Minimalistic Oracle contains a collection of practical examples from my encounters with Oracle technologies. When relevant, I also write about other technologies, like Linux or PostgreSQL. Many of the posts starts with "how to" since they derive directly from my own personal experience. My goal is to provide simple examples, so that they can be easily adapted to other situations.
Wednesday, April 20, 2022
Oracle vs PostgreSQL replication terminology
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment