Fri Jun 18 10:01:05 PDT 2010
- Previous message: [Slony1-general] Reasons to upgrade to Slony 2.0
- Next message: [Slony1-general] Replication time with 2.0.4rc2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Simon Riggs wrote: > I'm struggling to find an official answer to a fairly simple question: > > Why would I upgrade to Slony 2.0? > > That doesn't seem to be mentioned anywhere, I'm pretty sure I remember > reading it somewhere. > > I'm thinking by the time Slony 2.0 comes out, the new LISTEN/NOTIFY code > in Postgres 9.0 gives much reduced reason to upgrade. > > (Yes, I know the current status of 2.0.x - that is not the question) > > Thanks, > I gave a lightning talk on this at PGCon, you can see the slides http://wiki.postgresql.org/wiki/Image:02_slony.pdf (I think there should be a video of the lightning talks but I haven't seen them) The big reasons to go to 2.0 -You can make DDL changes without execute script -EXECUTE script doesn't automatically take an exclusive lock on every replicated table -Slony no longer messes with the catalog, this means you can do things like take a pg_dump from a replica -OMIT COPY and CLONE NODE allow you to populate your replicas through non slony means (ie pg_dump) -- Steve Singer Afilias Canada Data Services Developer 416-673-1142
- Previous message: [Slony1-general] Reasons to upgrade to Slony 2.0
- Next message: [Slony1-general] Replication time with 2.0.4rc2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list