Tue Apr 1 03:28:30 PDT 2008
- Previous message: [Slony1-general] Feature request for next slony version: initial replication of large DBs
- Next message: [Slony1-general] Feature request for next slony version: initial replication of large DBs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, April 1, 2008 12:02 pm, Andreas Kostyrka wrote: > One thing that should be also pointed out, that while a > pg_dump/pg_restore might be faster than slony initial copy, both use > basically the same mechanisms (COPY FROM/TO STDIN/STDOUT), so I'd guess > that you wouldn't shave to much of the initial replication time via > pg_dump. (Well, slony does need to get some locks to get going when I > remember right, which means that pg_dump/pg_restore has the potential to > be faster anyway.) OTOH, a filesystem level dump, can be, especially > when using LVM snapshots be produced rather quickly :) Exactly - dumping/restoring is but one option. For example, on our cluster slaves, we don't wast time manually installing the OS on each node - we install once, them dump that image onto slaves...
- Previous message: [Slony1-general] Feature request for next slony version: initial replication of large DBs
- Next message: [Slony1-general] Feature request for next slony version: initial replication of large DBs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list