Wed Dec 10 07:23:36 PST 2008
- Previous message: [Slony1-general] slonik_drop_sequence missing in 1.2.x series
- Next message: [Slony1-general] How to repair an (almost) broken cascading replication ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hannu Krosing a écrit : >> The only sure way is to just go through all nodes and manually clean up >> all sl_* tables referencing your new set (and possibly also all >> references to tables and sequences in these sets) I know how to suppress everything in sl_set/sl_table/sl_sequence. But I can easily guess it won't be enough. So how could I be sure I will delete all and only information concerning set 3 in other tables (sl_event may be the one I should focus on, no ?) ? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJP974A+REPKWGI0ERAm9LAJsH2GhvzROOlMyId7ZIi738WNUmPACbBCcj bjIoF4Hy9ygOYVJ1ru3Ph4w= =IHuZ -----END PGP SIGNATURE-----
- Previous message: [Slony1-general] slonik_drop_sequence missing in 1.2.x series
- Next message: [Slony1-general] How to repair an (almost) broken cascading replication ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list