Hi Andy, If you want help with resolving this, you need to give us some details.
1) What version(s) of slony / postgres are you running. 2) What did you do before making the change that you think broke your replication setup. Be as specific as possible. 3) What _exactly_ did you do that you think broke replication. Please provide the actual scripts, or as much details as you can manage. 4) Why do you think that broke replication (provide relevant excerpts from your slon logs, output from queries against the slony schema, etc) 5) What _exactly_ have you done since then? This will let us start to ask intelligent questions. Based on the little that you've told us, the first question that comes to mind is "did you use EXECUTE SCRIPT via slonik to make these schema changes"? Andrew On 3/30/07, Forum <[EMAIL PROTECTED]> wrote: > Hi to all, > > I have the following scenario: > DB1 -> is replicated to DB2 - set called replic_back - one server > DB2 -> is replicated ahead to DB3 - set called replic_loco. - second server > > Db2 and db3 are on the same machine(second server). > > Every time I make a schema change(alter table etc etc) in DB1 which is > successfully done in DB2 the replication replic_loco stops to work. The > schema change does not reach DB3. In the logs I didn't find anything > suspicios. If I make to replic_loco a unsubscribe and subscribe the data's > are actually refreshed, but the replication still does not work. > > > Please help, I'm in this problems since 2 months. > > Thanks, > Andy. > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://gborg.postgresql.org/mailman/listinfo/slony1-general > _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
