Dave Page wrote:



-----Original Message-----
From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 23 July 2003 14:00
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [pgadmin-hackers] pgadmin3 stops working when trying to access/show




Andreas, do you have any idea concerning this problem ? Does

anybody on

the list can reproduce such problems with other linux distros ?

Christian, I'll try to send you more precise informations concerning debian build so that you can try to build it by yourself...

But I won't

have time until tonight.



I'm quite sure that we have a libpq problem here. Christian reports that the query tool will not even return from a simple

SELECT rw.ev_class FROM pg_rewrite rw WHERE ev_class = 711967


which is really horrible. Only way I see is that Christian tries to figure it out on his system.



Yes, I'm seeing this on Snake, which has PostgreSQL 7.3.3, and out latest wx build.

If I do 'select * from pg_description', the query runs forever. Clicking
the stop button hangs pgAdmin. The edit grid just hangs at 'Refreshing
data, please wait'

Andreas, I'm unlikely to get time to look at this before I go, but I
have had some success running X and displaying the output remotely on my
laptop using Cygwin if you want to give that a go. The postgresql
installation is basically clean - you can open a trusted connection from
snake as user postgres.

BTW, it works fine on XP.

I wonder why this fundamental problem comes up at this late stage. Certainly it works on XP, as it does on W2K, and my SuSE 8.2 (2.4.20) has no problem either. One common thing is that the non-working systems use libpq from 7.3.3, maybe that's the problem. I'll be checking now with 7.4, before I try to ssh/X to snake. I tried snake's libpq.a on my system, but got unresolved externals.
Haven't run ssh/X so far, can you give me a short how-to? My f/w already maps port22 statically. If I didn't need ssh, I'd EXPORT DISPLAY=... and run.



Regards, Andreas


---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Reply via email to