Hi all, 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. Regards, -- Maciej Sobczak * www.msobczak.com * www.inspirel.com ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
