3 ms·

On this note, what is people's favorite way of scaling out Postgres? I'm told Slony + master/slaves configs are good for scaling out read-heavy situations, but

On this note, what is people's favorite way of scaling out Postgres? I'm told Slony + master/slaves configs are good for scaling out read-heavy situations, but it seems that there are a ton of alternatives on the market. Is there a comprehensive guide on the various options and tradeoffs for this kind of things? Good resources one could use to learn more about it?

gkelly 12y ago
The official PostgreSQL Documentation gives a good start, as well as explaining the many considerations involved in scaling. http://www.postgresql.org/docs/9.4/interactive/different-replication-solutions.html http://www.postgresql.org/docs/9.4/interactive/different-rep...
jeffdavis 12y ago
http://www.postgresql.org/docs/9.4/interactive/high-availability.html http://www.postgresql.org/docs/9.4/interactive/high-availabi... I recommend looking at streaming rep + hot stabdby first. Those are built in, officially supported by the project, lower administration effort and fewer pitfalls.
bmurphy1976 12y ago
Ugh, slony is awful. You use Slony when you have to do a live migration from one version to another (say 9.3 to 9.4) without any downtime. WAL replication is the way to go most of the time. I've used Londiste, it's better than Slony if you need partial replication, but still messy to use compared to WAL. Personally I haven't used any of the others (i.e. Bucardo).
- akurilin 12y ago
  Would you be so kind as to provide context on why WAL replication is superior to logical replication? I'm very interested in learning more about it. Also, what specifically did you hate about Slony? Any resources you'd recommend on this?
  - rpedela 12y ago
    WAL replication is currently the official and best supported mechanism for replication. If WAL replication does not suite your particular use case, then that is when to start looking at Slony, Bucardo, etc.

gkelly 12y ago

The official PostgreSQL Documentation gives a good start, as well as explaining the many considerations involved in scaling. http://www.postgresql.org/docs/9.4/interactive/different-replication-solutions.html http://www.postgresql.org/docs/9.4/interactive/different-rep...

jeffdavis 12y ago

http://www.postgresql.org/docs/9.4/interactive/high-availability.html http://www.postgresql.org/docs/9.4/interactive/high-availabi... I recommend looking at streaming rep + hot stabdby first. Those are built in, officially supported by the project, lower administration effort and fewer pitfalls.

bmurphy1976 12y ago

Ugh, slony is awful. You use Slony when you have to do a live migration from one version to another (say 9.3 to 9.4) without any downtime. WAL replication is the way to go most of the time. I've used Londiste, it's better than Slony if you need partial replication, but still messy to use compared to WAL. Personally I haven't used any of the others (i.e. Bucardo).

akurilin 12y ago
Would you be so kind as to provide context on why WAL replication is superior to logical replication? I'm very interested in learning more about it. Also, what specifically did you hate about Slony? Any resources you'd recommend on this?
- rpedela 12y ago
  WAL replication is currently the official and best supported mechanism for replication. If WAL replication does not suite your particular use case, then that is when to start looking at Slony, Bucardo, etc.