pgsql: Properly unregister OpenSSL callbacks when libpq is done with - Mailing list pgsql-committers

From mha@postgresql.org (Magnus Hagander)
Subject pgsql: Properly unregister OpenSSL callbacks when libpq is done with
Date
Msg-id 20081203200427.0A23B7545A4@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Properly unregister OpenSSL callbacks when libpq is done with
it's connection. This is required for applications that unload
the libpq library (such as PHP) in which case we'd otherwise
have pointers to these functions when they no longer exist.

This needs a bit more testing before we can consider a backpatch,
so not doing that yet.

In passing, remove unused functions in backend/libpq.

Bruce Momjian and Magnus Hagander, per report and analysis
by Russell Smith.

Modified Files:
--------------
    pgsql/src/backend/libpq:
        be-secure.c (r1.86 -> r1.87)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c?r1=1.86&r2=1.87)
    pgsql/src/interfaces/libpq:
        fe-secure.c (r1.110 -> r1.111)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-secure.c?r1=1.110&r2=1.111)

pgsql-committers by date:

Previous
From: achernow@pgfoundry.org (User Achernow)
Date:
Subject: libpqtypes - libpqtypes: final changes to error.c
Next
From: achernow@pgfoundry.org (User Achernow)
Date:
Subject: libpqtypes - libpqtypes: add man for PQgetErrorField, link to PQgeterror