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 STATUS : Retrieving server properties... (0.00 secs)
2004-10-11 15:20:26 INFO : Attempting to create a connection object...
2004-10-11 15:20:26 INFO : Creating a connect dialogue
2004-10-11 15:20:30 INFO : Destroying a connect dialogue
2004-10-11 15:20:30 STATUS : Connecting to database...
2004-10-11 15:20:30 INFO : Creating pgConn object
2004-10-11 15:20:30 INFO : Server name: 172.16.2.47 (resolved to:
172.16.2.47)
2004-10-11 15:20:30 INFO : Opening connection with connection string:
hostaddr='172.16.2.47' dbname='ts' user='test' password='password' port=5432
I've attached tcpdump's output of crashing session. Last client's
(172.16.2.49) packet is a TCP reset. My database has client_encoding =
'UNICODE'.
Virgil
> > 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.