Marco Gaiarin wrote: > As stated before, we use slony to replicate a postgres database, > backend for an internal webapp. > > That webapp are used only daily, and at predefined times we can easily > stop all the stuff involved. > > > To add a table to a replication, the only way is to add a new set and > then merge it? > Or if we stop slon daemons, or do something 'hard' like this, we can > circumvent it? > No, there isn't an alternative way; the way to add a table is to add a set, replicate it, and (if you like) merge it in.
Note that none of those steps require taking an outage (except for the brief time it takes to put the logtrigger on the table when you initially run SET ADD TABLE; that is unlikely to warrant an outage). _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
