On Tue, Jan 24, 2006 at 06:07:53PM -0500, Christopher Browne wrote: > Thus, you might have set #1, replicating from node 101 to node 102. > > And you have set #2, replicating from node 201 to node 202. > > Replication works fine with each set; it's just that confirmations don't > make it back, and so sl_log_1 never gets cleaned out :-(. > > If you aren't using that sort of "disjoint set" pattern of replication, > then you shouldn't have a problem.
Would simply subscribing all nodes to a table that never gets updated fix this as well? ISTM that might be easier than fiddling with listen_path... -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
