Thu Jun 9 14:52:32 PDT 2005
- Previous message: [Slony1-general] Subscribing when slave db is not empty
- Next message: [Slony1-general] Subscribing when slave db is not empty
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thursday 09 June 2005 00:46, John Surnow wrote:
> | All of the documentation I've read assumes that a slave db is empty
> | before the node subscribes to a cluster. What happens if the slave db isn't
> | empty (e.g., the slave is an up-to-date copy of the master)? Is the set
> | data on the slave deleted before new data is copied over from the master?
> yes; the slave does a "select truncateTable('yourtable');" before copying the
> data from the provider, which basically translates to a "delete from only
> yourtable".
I'm not sure that this is always the case. In our local configuration, I was
able to use pg_dump to get the schema and all current data from our publisher to
initialize a subscriber. I then installed the cluster config and started up
slony on both servers. Only new data is being pushed down.
--Sean
- Previous message: [Slony1-general] Subscribing when slave db is not empty
- Next message: [Slony1-general] Subscribing when slave db is not empty
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list