Обсуждение: Re: Cannot connect to postgresql 7.4.2
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Virgil Frum > Sent: 11 October 2004 11:23 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] Cannot connect to postgresql 7.4.2 > > pgAdmin3 ver. 1.2.0 Post Beta2 (Oct 09 2004) crashes when I'm > trying to connect to a postgresql 7.4.2 database. Same > behavior if I want to add a new server. Was tested only on > postgresql 8.0.0? No, I'm testing with 7.3.x & 8.0 at the moment (though admittedly not 7.4.x). Have you tried 8.0 yourself? Regards. Dave.
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Virgil Frum > Sent: 11 October 2004 16:24 > To: pgadmin-support@postgresql.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]. Regards, Dave.
Dave Page wrote: > > > >>-----Original Message----- >>From: pgadmin-support-owner@postgresql.org >>[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Virgil Frum >>Sent: 11 October 2004 16:24 >>To: pgadmin-support@postgresql.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
> -----Original Message----- > From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] > Sent: 11 October 2004 16:44 > To: Dave Page > Cc: Virgil Frum; pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Cannot connect to postgresql 7.4.2 > > Seems we'll have to hold RC1 until we're satisfied with libpq > situation (or distribute it statically linked, safety over size). Can't do that for pg_dump/pg_restore though. That's partly why I refactored large chunks of pginstaller, and updated pgAdmin to all use the same dynamic libpq. Regards, Dave
Dave Page wrote: > > > >>-----Original Message----- >>From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] >>Sent: 11 October 2004 16:44 >>To: Dave Page >>Cc: Virgil Frum; pgadmin-support@postgresql.org >>Subject: Re: [pgadmin-support] Cannot connect to postgresql 7.4.2 >> >>Seems we'll have to hold RC1 until we're satisfied with libpq >>situation (or distribute it statically linked, safety over size). > > > Can't do that for pg_dump/pg_restore though. That's partly why I > refactored large chunks of pginstaller, and updated pgAdmin to all use > the same dynamic libpq. No problem if pg_dump/pg_restore use dll, and pgadmin linked statically, we had this before. I'd really prefer being on the safe side; this is not the first time I shot somebody in the foot by garbling include libs and dlls (but it's the first time it was not mine :-) Regards, Andreas