Wed Aug 24 23:23:59 PDT 2011
- Previous message: [Slony1-general] how to fix replication after column added to origin outside Slony?
- Next message: [Slony1-general] how to fix replication after column added to origin outside Slony?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 25/08/2011 02:10, Jim Buttafuoco a écrit : > in general I agree, but sometimes you need to get the knife out... > IMHO you are free to do everything you want with your data. Even if you could lose them. These are your data. But you can't tell people that this is The good way of acting. You can, for sure, alter your tables outside of slony to add some column, on every node. Just be warned that the data of these columns may never be replicated as slony does not know everything on these. It is not the good way of handling DDL with Slony. Regards, - -- Stéphane Schildknecht Loxodata Contact régional PostgreSQL -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5V6n8ACgkQA+REPKWGI0HJhQCgq9vSY0HpjkP45zw6NqMZ4Re5 uzEAoMIyhHhaFelEYqmZnFsWr9WEtUUG =myWH -----END PGP SIGNATURE-----
- Previous message: [Slony1-general] how to fix replication after column added to origin outside Slony?
- Next message: [Slony1-general] how to fix replication after column added to origin outside Slony?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list