Dave Page wrote:
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 11 October 2004 16:44
To: Dave Page
Cc: Virgil Frum; [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] Cannot connect to postgresql 7.4.2
Seems we'll have to hold RC1 until we're sati
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 11 October 2004 16:44
> To: Dave Page
> Cc: Virgil Frum; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Cannot connect to postgresql 7.4.2
>
> Seems we'll have to hold RC1 unt
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Virgil Frum
Sent: 11 October 2004 16:24
To: [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] Cannot connect to postgresql 7.4.2
OK, I found out what's happening. I've been te
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Virgil Frum
> Sent: 11 October 2004 16:24
> To: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Cannot connect to postgresql 7.4.2
>
> > OK, I found out what's h
> 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
> hopefull
Virgil Frum wrote:
Hm, I don't see too much either.
Is that my win32 snapshot? Do you have a stack trace (Dr.Watson)?
Binary size (less than previous version): 5.500.928 bytes
The reason is that we now use libpq dynamically linked. The libpq
packaged in that zip should work with both pgAdmin and
> Hm, I don't see too much either.
> Is that my win32 snapshot? Do you have a stack trace (Dr.Watson)?
Binary size (less than previous version): 5.500.928 bytes (CRC32: 1DA3940B;
MD5: F86F0A85151495DD4C74EFA7DFBD9F89), timestamp: 09.10.2004 23:39:08. Dr.
Watson's stack trace attached.
Virgil
Stat
Virgil Frum wrote:
Debug logging doesn't seem to be useful in this case:
Hm, I don't see too much either.
Is that my win32 snapshot? Do you have a stack trace (Dr.Watson)?
Regards,
Andreas
---(end of broadcast)---
TIP 2: you can get off all lists at o
Debug logging doesn't seem to be useful in this case:
2004-10-11 15:20:26 STATUS : Retrieving server properties...
2004-10-11 15:20:26 INFO : Displaying properties for Server
172.16.2.47:5432
2004-10-11 15:20:26 INFO : Displaying properties for server
172.16.2.47:5432
2004-10-11 15:20:26 STATU
Virgil Frum wrote:
pgAdmin3 ver. 1.2.0 Post Beta2 (Oct 09 2004) crashes when I'm trying to
connect to a postgresql 7.4.2 database.
Please enable full logging to trace down the reason.
Regards,
Andreas
---(end of broadcast)---
TIP 7: don't forget to i
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Virgil Frum
> Sent: 11 October 2004 11:23
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] Cannot connect to postgresql 7.4.2
>
> pgAdmin3 ver. 1.2.0 Post Beta2 (Oct 0
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?
Postgres log:
Oct 11 13:10:59 linux postgres[2248]: [1-1] LOG: connection received:
host=172.16.2.49 po
12 matches
Mail list logo
