Description of problem: php-pgsql uses postgresql-libs which provides /usr/lib64/libpq.so.4 which has a memory leak which has since been fixed in postgresql84-libs which provides /usr/lib64/libpq.so.5.2 I want to request upgrade in php-pgsql from underlying postgresql-libs-8.1.21 (/usr/lib64/libpq.so.4) to postgresql84-libs-8.4.4 (/usr/lib64/libpq.so.5.2), please. Background on this request: Apache httpd's php's php-pgsql uses PostgreSQL 8.1 library (/usr/lib64/libpq.so.4), which leaks memory. PostgreSQL 8.4 library does not leak. Version-Release number of selected component (if applicable): 5.1.6 How reproducible: Run the 8.1 client against an 8.4 database for a while and watch the httpd process size. Steps to Reproduce: 1. install httpd, php, php-pgsql and postgresql-libs 2. install a postgres server 3. install an application that uses a postgres back end (like RT) 4. run it for a while and watch httpd process size swell Actual results: httpd process size grows without bound Expected results: for httpd process size to stay constant Additional info: the postgres client bug is fixed in libpq I am requesting an update to php-pgsql to use the fixed version, please. If there is any problem with this bug report / enhancement request, please let me know. Kind regards, Aleksey
The simple answer is "no", I'm afraid. The different versions of libpq expose the same symbols, so we must ensure they cannot be linked into the httpd process at the same time, since they would conflict. (e.g. it is possible for libpq to get linked into httpd via any of php, perl or mod_python) If you can identify the leak it might be possible to backport the fix to the 8.1 packages; do you have a minimal reproduction case?
Since we lack a reliable reproduction case, this bug will be closed. If you have issues impacting your use of Red Hat Enterprise Linux, please contact your support representative. Information about our production support process can be found at: http://www.redhat.com/support/process/