| From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | "Tony Caduto" <tony_caduto(at)amsoftwaredesign(dot)com> |
| Cc: | "Postgres General List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: msvcr80.dll and PostgreSQL 8.3 under Windows XP |
| Date: | 2008-02-18 15:58:35 |
| Message-ID: | 937d27e10802180758k5c0f367cnb4c7ea9ce4d38f34@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Feb 18, 2008 3:38 PM, Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2008-02-18 16:19:24 | Re: the feasibility of sending email from stored procedure in Postgres |
| Previous Message | Tony Caduto | 2008-02-18 15:38:33 | Re: msvcr80.dll and PostgreSQL 8.3 under Windows XP |