| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] libpq type system 0.9a |
| Date: | 2008-04-08 20:34:56 |
| Message-ID: | 47FBD6F0.8050607@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Martijn van Oosterhout wrote:
> How tight is the link to libpq? Could it exist as a seperate library:
> libpqbin or something? Still in core, just only used by the people who
> want it.
>
I gave this a lot of thought and I do think we could abstract this. The
idea is to complie it in or out.
Add a --with-typesys to configure, which could enable "#ifdef
LIBPQ_ENABLE_TYPESYS" everywhere. If you don't specify --with-typesys,
the API calls would still be there but would return ENOSYS, assign an
error string or something. This preserves link capatability.
This would trim out the 50k everyone is worried about :) I'm sure there
are other ways to acocmplish this, but this one seems easiest and keeps
it all centralized. Just like --with-openssl, except that loads
libcrypto.so.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2008-04-08 20:49:52 | Re: [PATCHES] libpq type system 0.9a |
| Previous Message | Bruce Momjian | 2008-04-08 20:32:03 | Re: [PATCHES] libpq type system 0.9a |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2008-04-08 20:40:59 | Fix \dT enum in psql |
| Previous Message | Bruce Momjian | 2008-04-08 20:32:03 | Re: [PATCHES] libpq type system 0.9a |