Wed Jan 29 09:21:04 PST 2014
- Previous message: [Slony1-bugs] [Bug 327] Sync failed right after initial copy
- Next message: [Slony1-bugs] [Bug 303] Slony Watchdog failed starting up the child process
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=327 Jan Wieck <janwieck at yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|low |urgent --- Comment #4 from Jan Wieck <janwieck at yahoo.com> 2014-01-29 09:21:04 PST --- I was able to reproduce the memory corruption and found what I believe is the place, where it happens. The code, that evicts an apply query form the cache when more than apply_cache_size different query plans are needed inside of a single SYNC processing, free'd data from the "new" cache entry, not the one to evict. The commit is here: https://github.com/wieck/slony1-engine/commit/6b56d480e211344eb952c9c23924ba555ac21d28 -- 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 327] Sync failed right after initial copy
- Next message: [Slony1-bugs] [Bug 303] Slony Watchdog failed starting up the child process
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list