Thu Jul 11 15:06:19 PDT 2013
- Previous message: [Slony1-bugs] [Bug 300] Would like to have some activity captured
- Next message: [Slony1-bugs] [Bug 301] New: memory leaks in slony 2.2.0 beta
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=300 --- Comment #2 from Christopher Browne <cbbrowne at ca.afilias.info> 2013-07-11 15:06:20 PDT --- An initial swing at this... https://github.com/cbbrowne/slony1-engine/tree/bug300 Things added: a) A new table, sl_eventlog b) A function that adds to it, logEvent() c) Injected logEvent() into existing function component_state(), so that the existing monitoring of state pushes that data into sl_eventlog d) Injected some calls into logswitch_finish() so that log switches get captured e) Add a cleanup function, trimOldLoggedEvents() For each actor/eventtype, it trims out all entries older than the last N, where N is currently set to 10. f) Add a call to that function to cleanupEvents(), so that the log gets trimmed. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
- Previous message: [Slony1-bugs] [Bug 300] Would like to have some activity captured
- Next message: [Slony1-bugs] [Bug 301] New: memory leaks in slony 2.2.0 beta
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list