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
Server-side memory leak in PostgreSQL #19
Comments
Can you confirm use are using prepared statements? Unfortunately, the fix is causing regression. You can take a look at detailed explanation posted in the issue #13 |
yes. I have use prepared statements (for rowset only). |
And, can you confirm you have tried the source code with the fix for prepared statement leak applied. Namely, are you using SOCI with 02bb841b changes? |
Yes. I confirm. I have use TODAY master. And I in real-time see (top), that postgres process eats 100KB per second (I do prepare every second). |
I use prepare only in this construction: |
The fix has been merged into master SHA1: 8c05035 Thank you! |
I try use SOCI in my project. But after some time I found, that SQL server (postgresql-8.4, 9.1, and 9.2) has eat all memory and killed by oom-killer. After some investigations I update library to recent master (today). But problem not fixed yet.
The text was updated successfully, but these errors were encountered: