Andrew Chernow wrote: > Your method would work as well. The only issue is you still have the > same issue of binary distributed libpqs. Would redhat distribute a > binary linked with libpqtypes? If not, you have the same issue of the > end-user having to compile libpq ... passing -lpqtypes to the linker. > If redhat did link it, you run into the disk space complaint all over again. > > My suggestion was trying to work around this by dynamically loading the > library, PQtypesEnable(TRUE). In this model, redhat doesn't even have > to distribute libpqtypes.so (considering the disk space issue). It > could be easily be an additional download. All you need are some proxy > functions inside libpq, PQputf calling a dynamically loaded function. > This passes the disk space complaints and doesn't require a re-compile > if an end-user wants to use it.
I don't see requiring users to add -lpqtypes to use these functions as a problem. The idea is that the default libpq would have enough hooks that you could use it without modification. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
