Fri Jan 16 15:02:25 PST 2009
- Previous message: [Slony1-bugs] Re: sl_log_1/2 not switching
- Next message: [Slony1-bugs] Bugs in scripts of Slony1 2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
John Stockdale <jstockdale at videosurf.com> writes: > FYI: We came across the same issue, and were tempted to make this > exact modification. > > Chris: Can you double check the logic in this function. I don't ever > see the log_txid get smaller (due to the cleanup thread no longer > deleting entries from the table), so the condition is never met in > 2.0. If you manually truncate the log or force the cleanup thread to > delete entries like it did in 1.2, it works, but this kills > performance and defeats the purpose of trying to truncating the table. Yes, indeed, that describes the issue correctly. Evidently I looked a little *too* literally at the code in cleanupEvent(), where it uses the very same WHERE clause to see what data should get deleted from sl_log_[12]. :-( I have committed this change as suggested. http://lists.slony.info/pipermail/slony1-commit/2009-January/002423.html -- (format nil "~S@~S" "cbbrowne" "linuxdatabases.info") http://www3.sympatico.ca/cbbrowne/oses.html "MS Windows is the computer equivalent of burger chains and bowling lanes. It is software that "works" only if you lower your expectations to a point where you have essentially buried them." -- Sam
- Previous message: [Slony1-bugs] Re: sl_log_1/2 not switching
- Next message: [Slony1-bugs] Bugs in scripts of Slony1 2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list