On 7 October 2012 23:06, Maciej Sobczak <[email protected]> wrote: > > I was contacted by one of our users who was experiencing a strange > memory leak on the server side in PostgreSQL. > > Yes, server-side, not client-side. After some longer period of time the > memory occupied by the server process that handled the given client > connection was always growing. > > It appeared to be a problem caused by the prepared statement mechanism, > which is handled by the PQprepare function. This function allocates some > resources on both client- and server-side and later uses them to > execute, potentially multiple times, the named statement. There is no > libpq function to deallocate these resources and an explicit SQL-level > command is needed to do it. > > The following commit fixes that (I hope): > > http://soci.git.sourceforge.net/git/gitweb.cgi?p=soci/soci;a=commit;h=02bb841bbc6d8d6306133ca4b4d8557d71031349 > > Let me know if you still experience any similar memory problem.
Maciej, This commit seems to cause another problem, see my bug report: https://github.com/SOCI/soci/issues/13 and my other message where I tracked it down: https://sourceforge.net/mailarchive/message.php?msg_id=30028550 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ The Windows 8 Center - In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
