Noel J. Bergman wrote:
Attached is a first pass at an attempt to fix. I have reviewed it, and
provided it directly to Stefano to review and try.
I have NOT tried it on my system, yet, and won't put it on my production
server for a while because I am trying to keep the current process going to
verify the lack of memory leaks. But I want to get this out for review
ASAP, before I have time to do some bench testing.
--- Noel
I reviewed the code and it seems ok.
It is less than perfect but it is the less of the evil for fix this
issue for 2.3.0.
My only concern is about the removal of setMaxRows: unfortunately the
only big system where I plan to put this patch soon is on mysql5 and
connector/j 5 and I believe they correctly handle this scenario but I
would like to know what happen on a mysql 3 with connector 3.0 and big
spools.
I think this patch should be committed to 2.3 branch and that we'll need
a few weeks to update our production servers and have at least a bunch
of servers using the code we're going to release as 2.3.0 before
starting the vote.
I plan to be able to put this one on 3 servers: 2 using mysql (4 and 5)
and 1 using files only. Only the mysql 5 server have big traffic.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
