Scott Marlowe wrote: >> >> The only way to accomplish this would be to split the table into two, >> where the data that needs to be replicated is in one table, and the >> other data can remain in the other. >> > > Actually, inheritance might help out here. > Both table design approaches are possible, _if_ the application allows that. The more intuitive way would be if Slony 1.3 or so supports a restriction clause in sl_table. It's not uncommon to have a central db with satellites that receive a fraction of the data each, determined by various criteria. Not touching data structures, but defining some replication meta data is much less painful for that job.
Regards, Andreas _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
