Andrew Chernow wrote:
> Alvaro Herrera wrote:
>> Andrew Chernow wrote:
>>
>>> Forgot to say: There is stuff in PGconn, PGresult, PQclear,
>>> PQfinish (maybe a couple other places).
>>
>> Maybe there's a way we can have libpqtypes adding calls into some
>> hypothetical libpq hooks. So libpqtypes registers its hooks in _init()
>> or some such, and it gets picked up automatically by any app that links
>> to it.
>>
>
> Kinda what my last suggestion was. Some tid-bits need to be reside in
> libpq, but very little. I was thinking PQtypesEnable(bool) which
> would dlopen libpqtypes and map all functions needed. This would
> leave the function bodies of PQputf, PQgetf, PQparamExec, etc... as
> simple proxy functions to the dynamically loaded functions. This
> removes any bloat that people don't like right now but still allows
> one to use libpq as the primary interface, rather than having to
> fiddle with libpq and some other API.
Please make sure that any scheme you have along these lines will work on
Windows DLLs too.
cheers
andrew
