-
Notifications
You must be signed in to change notification settings - Fork 562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FetchMany MemoryError #25
Comments
Seems to be working fine for |
I have pyodbc in a number of 24x7 servers and do not see any evidence of leaks. Is this still occurring? I'm going to close this, but please reopen if you found anything. |
I made 4.0.15 yesterday to fix that. Please try that version.
…On Mar 16, 2017, 7:46 AM -0500, ZaM-Rai ***@***.***>, wrote:
I'm getting this error after about 24 hours of running my DB.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub (#25 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AABrHXSpN5rab8BY1g9WZHlPTvt1ZJNCks5rmS8UgaJpZM4CJQKZ).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using an iterator with fetchmany to stream a large result out as CSV:
For a large query, I can only get 3641 rows out of ~4300 before
fetchmany
throws a MemoryError.I've tried a variety of array sizes, as well as
fetchone
. The error is consistent.I've also monitored memory usage for the process and I'm not entirely convinced there is a legitimate memory error: physical memory remains stable around 25 megs, virtual at 2.5 gb. At no point do I get any telltale signs of a machine running out of memory.
Any thoughts?
The text was updated successfully, but these errors were encountered: