Fri Sep 23 17:03:48 PDT 2005
- Previous message: [Slony1-general] Master or Salave Down
- Next message: [Slony1-general] Master or Salave Down
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marcelo Michalek <memichalek at gmail.com> writes: > DB1 (Master) DB2 (Slave) > down > ----- promote DB2 (Master) (Lost the last > commited > transactions) > Master Back > DB1 (Slave) <------------------ DB2 (Master) > reinitializing from scratch > promote as Master again (clean process) > DB1 (Master) DB2 (Slave) > > Is it OK? That appears to describe how things would work, yes. > So, there is no way to promote again the first Master without a > complete reconstruction of the database from scratch (not from Check > Point or somthing like that) There are other replication tool that > make this? Feature request #1389 outlines a "clone a database" approach which should in principle speed up the reconstruction. http://gborg.postgresql.org/project/slony1/bugs/bugupdate.php?1389 I probably won't have time to work on that until November... -- output = ("cbbrowne" "@" "ca.afilias.info") <http://dev6.int.libertyrms.com/> Christopher Browne (416) 673-4124 (land)
- Previous message: [Slony1-general] Master or Salave Down
- Next message: [Slony1-general] Master or Salave Down
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list