Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm planning to migrate from MySQL to PostgreSQL, but worried about the apparent luck of replications solutions there.

Are there any current replication techniques that can be used out of box?

Heartbeat/DRBD would probably work, but I'm looking for approaches that are more integrated in PostgreSQL itself.

share|improve this question
i like this one: 'the replication options for PSQL are agricultural to say the least' [ from ] ;-] – pQd Jan 5 '10 at 19:27
Yep, I seen this as well. Not very encouraging :( – SyRenity Jan 6 '10 at 11:56
up vote 4 down vote accepted

For available replication solutions, see for instance,_Clustering,_and_Connection_Pooling.

But no, there is nothing at the moment that works "out of the box".

PostgreSQL 8.5, currently in development, will contain a built-in replication feature that is known under the name "Hot Standby". See for example

share|improve this answer
This looks interesting - will the switch be automatic, and the "hot standby" node will become the master? Also any ETA for the 8.5 stable? Thanks. – SyRenity Jan 6 '10 at 11:57
No, the hot standby feature only arranges the replication of the data and receives notice when the slave should become the master. But you will have to trigger the switching yourself, using Heartbeat or UCARP or something like that. It's not exactly plug-and-play. – Peter Eisentraut Jan 6 '10 at 21:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.