On Feb 18, 2008 3:38 PM, Tony Caduto <tony_caduto@amsoftwaredesign.com> wrote:
> Dave Page wrote:
> >
> > You can avoid this by building your own libpq.dll using mingw/msys if
> > you like - that will work just fine with a VC++ built server.
> >
> >
>
> Hi Dave,
> Just some thoughts on the whole libpq.dll thing.
>
> It would be really nice from a client distribution view of things to
> have a libpq.dll that was not so dependency heavy.
> For the 8.3 release the total amount of files needed to use things such
> as pg_dump.exe is close to 5mb.
>
> maybe a light version of libpq.dll is needed, just the libpq and the
> open ssl dlls would be ideal, many times all that extra stuff is not
> needed just to run pg_dump.
>
> Didn't there used to be a project on pgfoundry that built the client
> tools separate from the server build?
I think so. From our perspective though we need to ensure that libpq
will support the same options as the server we ship (for example, I
know people that do need Kerberos support) - bundling two different
builds will doubtless create confusion.
Maybe you should consider reviving that project?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
