Wed Dec 20 11:46:21 PST 2006
- Previous message: [Slony1-general] how to troubleshoot/fix slow initial replication --
- Next message: [Slony1-general] how to troubleshoot/fix slow initial replication --
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Dec 20, 2006, at 10:13 AM, Norman Yamada wrote: > Yesterday, I dropped one of the slave nodes from the cluster and > built postgresql 8.2.0 on it. I then killed all the slon processes, > upgraded master and both slave boxes to slony 1.2.2, brought back up > the slony cluster and readded the second slave back to the node. Do you have any indexes on the new replica? Try without any indexes other than the PK and then add them later. Adding/removing indexes is safe to do outside of the slony DDL change mechanism, provided they don't add any more strictness to the data than the master has (ie, no additional unique indexes). Slony is supposed to disable the indexes but perhaps it is not for some reason. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2530 bytes Desc: not available Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20061220/ce4e2230/attachment.bin
- Previous message: [Slony1-general] how to troubleshoot/fix slow initial replication --
- Next message: [Slony1-general] how to troubleshoot/fix slow initial replication --
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list