On Sun, Dec 09, 2007 at 11:09:13PM +0000, Peter Geoghegan wrote: > David, > > Unfortunately, changes to the database may be quite varied. We > aren't talking about massive amounts of data though - in the order a > few dozen rows per update per slave. Confining that to a single > transaction isn't realistic, though.
I don't know how to put this to you gently, but it doesn't seem to me that your design goals are terribly well thought-out. Could you explain in short simple words what's wrong with having Slony simply do its job, which is to ship out row changes at the transaction boundary? Cheers, David. -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: [EMAIL PROTECTED] Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
