Mon Jan 28 11:34:27 PST 2008
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide testbed.sgml
- Next message: [Slony1-commit] slony1-engine/doc/adminguide slony.sgml filelist.sgml triggers.sgml
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide In directory main.slony.info:/tmp/cvs-serv5899 Modified Files: slonik_ref.sgml Log Message: Add notes regarding requirement for CLONE NODE that there be synchronization against SYNCs against other nodes Index: slonik_ref.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v retrieving revision 1.77 retrieving revision 1.78 diff -C2 -d -r1.77 -r1.78 *** slonik_ref.sgml 21 Jan 2008 19:27:37 -0000 1.77 --- slonik_ref.sgml 28 Jan 2008 19:34:25 -0000 1.78 *************** *** 3029,3037 **** standard database tools. </para> </Refsect1> <Refsect1><Title>Example</Title> <Programlisting> clone prepare (id = 33, provider = 22, comment='Clone 33'); ! </Programlisting> </Refsect1> <refsect1> <title> Version Information </title> --- 3029,3047 ---- standard database tools. </para> + + <para> Note that in order that we be certain that this new node be + consistent with all nodes, it is important to issue a SYNC event + against every node aside from the provider and wait to start + copying the provider database at least until all those SYNC events + have been confirmed by the provider. Otherwise, it is possible + for the clone to miss some events. </para> + </Refsect1> <Refsect1><Title>Example</Title> <Programlisting> clone prepare (id = 33, provider = 22, comment='Clone 33'); ! sync (id=11); ! sync (id=22); ! </Programlisting> </Refsect1> <refsect1> <title> Version Information </title>
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide testbed.sgml
- Next message: [Slony1-commit] slony1-engine/doc/adminguide slony.sgml filelist.sgml triggers.sgml
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list