>This is not required for adding new tables that stand alone (ie have not FKs) >or for function >definitions.
Not necessarily true. Simply put, if you want your slaves to stay in sync with the master, I highly recommend you use EXECUTE SCRIPT to propagate changes across all nodes. Even if the new object will not be immediately replicated, it's always best to insure schemas are identical on all nodes. Note: There is no requirement to do this, just good practice. If you forget to manually create a table on all nodes and then add it to replication later, it will definitely bite you where i hurts. And if you have to fail over and the object isn't there, can you say for sure things will be fine? Melvin Davidson ________________________________ From: Vick Khera <[email protected]> To: slony <[email protected]> Sent: Monday, October 5, 2009 1:10:26 PM Subject: Re: [Slony1-general] when creating new table with FK reference to existing replicated table, do I need to run via EXECUTE SCRIPT? On Mon, Oct 5, 2009 at 11:07 AM, Melvin Davidson <[email protected]> wrote: >>Does that create table command need to be run via EXECUTE SCRIPT in slony1? > > Yes. Whenever you create or modify objects, you should always use EXECUTE > SCRIPT. > Doing so insures that the changes are propagated across all nodes. This is not required for adding new tables that stand alone (ie have not FKs) or for function definitions. _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
