Comparing MySQL and Postgres 9.0 Replication
Nov 18, 2010, 23:34 (0 Talkback[s])
(Other stories by Robin Schumacher, Gary Carter)
"Replication is one of the most popular features used in RDBMS's
today. Replication is used for disaster recovery purposes (i.e.
backup or warm stand-by servers), reporting systems where query
activity is offloaded onto another machine to conserve resources on
the transactional server, and scale-out architectures that use
sharding or other methods to increase overall query performance and
data throughput.
"Replication is not restricted to only the major proprietary
databases; open source databases such as MySQL and PostgreSQL also
offer replication as a feature. While MySQL has offered built-in
replication for a number of years, PostgreSQL replication used to
be accomplished via community software that was an add-on to the
core Postgres Server. That all changed with the release of version
9.0 of PostgreSQL, which now offers built-in streaming replication
that is based on its proven write ahead log technology.
"With the two most popular open source databases now providing
built-in replication, questions are being asked about how they
differ in their replication technologies. What follows is a brief
overview of both MySQL and PostgreSQL replication, with a brief
compare and contrast of the implementations being performed
immediately afterwards."
Complete Story
Related Stories:
- How To Set Up An Active/Passive PostgreSQL Cluster With Pacemaker, Corosync, And DRBD(Nov 18, 2010)
- A report from OpenSQLCamp(Nov 16, 2010)
- Lessons from PostgreSQL's Git transition(Oct 27, 2010)
- Server Configuration Tuning in PostgreSQL(Oct 22, 2010)
- Saving Yourself with Data Replication(Oct 20, 2010)
- Five Enterprise Features in PostgreSQL 9(Oct 01, 2010)
- PostgreSQL 9.0 arrives with many new features(Oct 01, 2010)
- Memcached Gets NoSQL in Membase(Jun 25, 2010)