Streaming replication replicates schema changes, which iirc, Slony does
not. That could be bloat as well, but I find it pretty useful.
Justin Hopkins
Manager Information Technology
573-808-2309
On Fri Dec 21 14:50:37 2012, Dan Scott wrote:
On Fri, Dec 21, 2012 at 12:24:37PM -0800, Joshua D. Drake wrote:
Hello,
So I was told that if I was able to rip slony out for replication of
PostgreSQL with Evergreen, that the Evergreen community would be
interested in this.
Well, you can, easily. If you are running PostgreSQL 9.0 or above,
you do not need Slony as long as you are replicating the full
database. Further, replication can be synchronous and yes, it works
with PgPool for load balancing. All you need is Hot Standby.
The benefits are:
Easier upgrades
Easier management
Better Stability
One less external component
Very easy backups
True High Availability
Right-o. And some of us have written about (and have been using)
streaming replication since shortly after 9.0 came along. I wrote a
9.0 approach up in July 2011 at
http://bzr.coffeecode.net/replication9/postgresql-9-replication.txt and
a hasty intro to a 9.1-based method in Evergreen in Action a couple of
weeks ago:
http://en.flossmanuals.net/evergreen-in-action/care-and-feeding-of-evergreen/
I guess the downside that some sites see with streaming replication vs.
Slony is that you get all of the bloat of the auditor tables, etc,
because you have to replicate the entire database. Not a problem for our
installation, but an issue for others.
