Re: Cannot connect to postgresql 7.4.2

Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: pgadmin-support-owner(at)postgresql(dot)org
>>[mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Virgil Frum
>>Sent: 11 October 2004 16:24
>>To: pgadmin-support(at)postgresql(dot)org
>>Subject: Re: [pgadmin-support] Cannot connect to postgresql 7.4.2
>>
>>
>>>OK, I found out what's happening. I've been testing with
>>
>>the correct
>>
>>>versions from
>>>
>>
>>http://pgadmin.postgresql.org/snapshots/postgresql/libs-win32-
>>20040927.zip
>>
>>> but my distribution batch copied older versions.
>>>
>>>Please download that zip, replace the dlls and try again. This will
>>>hopefully fix the problem; I'll upload a corrected snapshot tonight.
>>
>>Downloaded and tested. It's nice to see that things are
>>working as expected.
>>Thanks.
>
>
> Glad it's working. I should point out that it's possible we may see
> another breakage here before long. I discovered that the exports from
> VC++/Borland and Mingw builds of libpq.dll don't match. Magnus Hagander
> has been playing with the Mingw build to make it share a .def file with
> VC++ which appears to be working, but following discussion with Tom
> Lane, he is currently reviewing the exported API to figure out exactly
> what is and what isn't needed. Oh, and just to put the icing on the
> cake, the default, non-ssl build has an intentionally different API from
> the ssl build that we use (and ssl symbols are not exported at all by
> the VC++/Borland DLLs, even if built with SSL support!).
>
> Anyway, once that little lot has been sorted out, I'll post an updated
> libpq.[lib|dll].

Seems we'll have to hold RC1 until we're satisfied with libpq situation
(or distribute it statically linked, safety over size).

Regards,
Andreas