Tue Feb 28 08:12:56 PST 2012
- Previous message: [Slony1-general] Slony replication stops right after start
- Next message: [Slony1-general] Slony replication stops right after start Slony replication stops right after start
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2/24/2012 8:12 AM, Ulas Albayrak wrote: > Let's say I have set up the whole replication system and then at 12:00 > I start the actual replication. Around 12:05 copying of table A from > node 1 to node 2 starts. It finishes but only the data that was > received before 12:05 get copied to node 2. Then at 12:10 copying of > table B starts. Same thing here: Slony copies all the data that was > received before 12:10 to node 2. And this is the same for all tables. This should only happen if both tables belong to different sets. If they belong to the same set, they are copied with the same snapshot inside the same transaction processing the ENABLE_SUBSCRIPTION event. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] Slony replication stops right after start
- Next message: [Slony1-general] Slony replication stops right after start Slony replication stops right after start
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list