In response to Ow Mun Heng <Ow.Mun.Heng@xxxxxxx>: > > I'm just wetting my hands with slony and during the setup of the slave, > I did and dump and restore of the master DB to the Slave DB. > > However during the startup of slony, I noticed that it issues a truncate > command to the (to be) replicated table. Hence, this means that there's > no such need for me to do a dump/restore in the 1st place. > > can someone confirm this? Confirmed. It's how Slony is designed to work. > It _is_ taking long time (for slony) to do the > \copy (~60GB in multiple tables being replicated, including (on the fly) > index creation) 1) It only needs to be done once 2) You can remove the indexes from the replica and add them back in after the initial sync is complete. -- Bill Moran http://www.potentialtech.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
