Thu May 15 00:51: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 ]
Fair enough. Sorry if I offended anyone. We've been using Slony at www.redfin.com for a few months now, and it gets the job done for us, so thank you to everyone who contributed to this project. --S -----Original Message----- From: Simon Riggs [mailto:simon at 2ndquadrant.com] Sent: Thursday, May 15, 2008 12:51 AM To: Shahaf Abileah Cc: slony1-general at lists.slony.info Subject: Re: [Slony1-general] Using Postgres' continuous archiving andpoint-in-time recovery as a form of replication On Wed, 2008-05-14 at 20:00 -0700, 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? Those are correct but of course whether they are advantages or disadvantages depends upon the situation and your requirements. Slony has many features designed to fine-tune the replication process, so the phrase "more natural manner" isn't fair. "without needing to run a command" would be more neutral viewpoint. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com
- 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