Fri May 16 07:16:32 PDT 2008
- Previous message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Next message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 05:00 15/05/2008, Shahaf Abileah wrote: >By the way, if it can, it seems that: >1. It would have the advantage that various operations are >handled in a more natural manner than with Slony (e.g. DDL) >2. It would have the disadvantage that you can't be choosy >about what to replicate you get the entire DB cluster, or nothing at all. >Is that correct? AFAIK, another important drawback is that you can't use it between different (major) versions of Postgresql, or different platforms (at the very least platforms with different word sizes, alignment constraints, byte order, etc., but also different compile-time settings...), as it's a binary format based on the on-disk representation of data. So you can't use it for transparent upgrade scenarios. Correct me if I'm wrong. Jacques.
- Previous message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Next message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list