Customer found that connections to a PostgreSQL database via a SSL secured connection leaks memory in the client. Problem was traced to an error in the close_SSL() functionin backendd/libpq/be-secure.c. Information regarding the defect can be found at http: //archives.postgresql.org/pgsql-bugs/2003-12/msg00118.php http: //archives.postgresql.org/pgsql-bugs/2003-12/msg00167.php The attached patch has been adapted for the RHEL3 package rh-postgresql-7.3.15-2.src.rpm from the fixes proposed in those messages. The patch has been tested by the customer and shown to resolve the issue. Customer would like an official package.
Created attachment 131204 [details] postgresql-free-ssl.patch
This is a trivial fix from an engineering perspective, but sliding it into U8 at this late date will require jumping through the exception-process hoops. I believe the first step is for SEG to make the exception request, so ball's in your court.
Fix is built in dist-3.0E-qu-candidate, rh-postgresql-7.3.15-3. Will file an errata as soon as someone tells me the exception is approved.
PM ACK for 3.9
The fix for this is included in rh-postgresql-7.3.18-1, which has just been pushed as part of RHSA-2007:0064. So we no longer need consider it for an update release.