Tue Oct 26 11:24:24 PDT 2010
- Previous message: [Slony1-commit] Slony-I-commit Documentation patch. Mention that slony likes to take e
- Next message: [Slony1-commit] slony1-www/downloads/1.2/source slony1-1.2.21-docs.tar.bz2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-www/content In directory main.slony.info:/tmp/cvs-serv22448 Modified Files: frontpage.txt Log Message: Add discussion of "why is Slony still relevant?" Index: frontpage.txt =================================================================== RCS file: /home/cvsd/slony1/slony1-www/content/frontpage.txt,v retrieving revision 1.42 retrieving revision 1.43 diff -C 2 -d -r1.42 -r1.43 *** frontpage.txt 7 Oct 2010 16:57:59 -0000 1.42 --- frontpage.txt 26 Oct 2010 18:24:22 -0000 1.43 *************** *** 1,7 **** --- Slony-I 2.0.5 Released - <p> ! 2.0.5 fixes more than 24 issues found from 2.0.4 and earlier versions, remedying many issues found during an extensive testing period. --- --- 1,43 ---- --- + Why use Slony-I when PostgreSQL 9.0 includes replication? + + <P> PostgreSQL 9.0 includes streaming replication, which, for a number + of use cases, is likely to be simpler and more convenient than + Slony-I. + + <P> There are, however, three characteristic kinds of cases where + you'll need something like Slony-I, where the built-in WAL-based + replication won't work: + + <ul> + + <li> You need to interact between PostgreSQL versions. Slony (and + similar systems like Londiste and Bucardo) can cope with having + nodes running different versions of PostgreSQL. + + <P> WAL-based replication requires that all databases use + <i>identical</i> versions of PostgreSQL, running on identical + architectures. + + <li> You only want to replicate parts of the changes that are going on. + + <P> WAL-based replication duplicates <i>absolutely everything.</i> + + <li> You need for there to be extra behaviours taking place on + subscribers, for instance, populating cache management information. + + <p> WAL-based replication duplicates <i>absolutely everything,</i> and + nothing extra that changes data can run on a WAL-based replica. + + </ul> + + <P> Steve Singer also discusses the matter in <a href= + "http://scanningpages.wordpress.com/2010/10/09/9-0-streaming-replication-vs-slony/> + 9.0 Streaming Replication vs Slony </a>. + + --- Slony-I 2.0.5 Released ! <P> 2.0.5 fixes more than 24 issues found from 2.0.4 and earlier versions, remedying many issues found during an extensive testing period. --- *************** *** 27,32 **** --- Slony-I 2.0.4 Released ! <p> ! This release of the 2.0.x stream includes fixes to the issues introduced in 2.0.3. 2.0.3 installations are encourged to upgrade. --- 63,68 ---- --- Slony-I 2.0.4 Released ! ! <p>This release of the 2.0.x stream includes fixes to the issues introduced in 2.0.3. 2.0.3 installations are encourged to upgrade.
- Previous message: [Slony1-commit] Slony-I-commit Documentation patch. Mention that slony likes to take e
- Next message: [Slony1-commit] slony1-www/downloads/1.2/source slony1-1.2.21-docs.tar.bz2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list