what does that re expect to replace? If its expecting e.g. per-line, then running it on each line of the sql might avoid whatever pathological behaviour is occuring.
Another possibility is that the oops updater isn't very efficient on memory and this OOPS report simply shows that up. How much memory do we typically use per OOPS, and do we free it all after each OOPS?
what does that re expect to replace? If its expecting e.g. per-line, then running it on each line of the sql might avoid whatever pathological behaviour is occuring.
Another possibility is that the oops updater isn't very efficient on memory and this OOPS report simply shows that up. How much memory do we typically use per OOPS, and do we free it all after each OOPS?