just alter the table on the other node, I have to do it here all the time.

On Aug 24, 2011, at 6:24 PM, maretranq wrote:

Hello,

Is it possible to fix this situation, ideally without starting over?

A Slony cluster of 2 nodes was deployed and running. Some time later,
a column was added only to the origin/"master" node outside of Slony
control. slon is still running on both nodes, but the subscriber node
is understandably emitting errors, such as:

ERROR:  column "foo" of relation "bar" does not exist

Does anyone have suggestions on what might be the best way forward?

Software versions:

Ubuntu 10.04
PostgreSQL 8.4.8 (Ubuntu)
Slony-I 1.2.20 (Ubuntu)

I apologize if this scenario has been addressed previously; I'd
greatly appreciate any pointers. What searches I tried did not turn up
something applicable.

Thanks!

mare
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general


___________________________________________________________







Jim Buttafuoco
[email protected]
603-647-7170 ext. 2222- Office
603-490-3409 - Cell
jimbuttafuoco - Skype







_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general

Reply via email to