Re: [pgadmin-support] SSH tunnel key exchange methods

> The key exchange methods offered when opening an SSH tunnel are all > SHA1 and therefore too weak: > > [sshd] fatal: Unable to negotiate with xxx.xxx.xxx.xxx: no matching > key exchange method found. Their offer: > diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1, > diffie-hellman

[pgadmin-support] SSH tunnel key exchange methods

Hi The key exchange methods offered when opening an SSH tunnel are all SHA1 and therefore too weak: [sshd] fatal: Unable to negotiate with xxx.xxx.xxx.xxx: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1, diffie-hellman-group1-s

Re: [pgadmin-support] pgAdmin 1.18.0 + slony-I 2.2.0 + PG 9.3

Hi, Thanks for the feedback. I'm looking forward to this update. Any idea on when it will be released? regards, Sven 2013/10/11 Neel Patel > Hi Sven, > > Sorry for the late replay, we have checked and it is a bug in pgAdmin > because the name of the sql files got changed in

[pgadmin-support] Postgres 9.3 + Slony-I 2.2.0 + PgAdmin 1.18.0 on Windows Server 2003 R2 Enterprise 32 Bit

Hello there, I am getting pretty frustrated. Is the above combination tested? I still get 'Slony-I creation scripts not available'... I really need to get replication running... Regards, Sven

Re: [pgadmin-support] pgAdmin 1.18.0 + slony-I 2.2.0 + PG 9.3

slony scripts reside. Sven 2013/9/29 Guillaume Lelarge > On Sun, 2013-09-29 at 21:13 +0200, Sven Meirsman wrote: > > Hello, > > > > I am having difficulties getting the slony-i scripts recognized and found > > by pgAdmin, > > > > I am running > > - Wind

[pgadmin-support] pgAdmin 1.18.0 + slony-I 2.2.0 + PG 9.3

However, like stated above, things are setup correctly. Can someone help me out on this issue? regards, Sven

[pgadmin-support] unsubscribe

unsubscribe Produktentwicklung Gölz & Schwarz GmbH Waltherstr. 29, 80337 München, Germany phone: + 49 - (0)89 / 54 46 70 - 0 fax: +49 - (0)89 / 54 46 70 - 10 e-mail: [EMAIL PROTECTED] web: http://www.goelz.com

[pgadmin-support] configure checks for headers in include/wx-2.5/wx

Hi, configure checks for headers in inlcude/wx-2.5/wx, but you compile wxGTK-2.5.2beta, the headers are in include/wx, so configure should have a better check to locale wx-headers. Thx Sven ---(end of broadcast)--- TIP 4: Don't 'ki

Re: [pgadmin-support] pgAdmin III

Sven, what you didn't mention is that you're probably using the German language setting. There was a translation of "%d rows." into "%s Zeilen." which is obviously the highway to hell. OK - so - why did pgAdmin crash? will the code be fixed? pgAdmin should

Re: [pgadmin-support] pgAdmin III

: hostaddr=127.0.0.1 dbname=test user=Sven port=5432 2003-06-19 23:49:55 INFO : Setting client_encoding to 'UNICODE' 2003-06-19 23:49:55 INFO : Creating EditGrid 2003-06-19 23:49:55 INFO : Running query SELECT Oid, * FROM public.test ORDER BY test 2003-06-19 23:49:55 QUERY : Th

Re: [pgadmin-support] pgAdmin III

So i should add one: If i try to view a table with pgAdminIII (by klicking on the sunglasses or by doing a "select *" in the SQL window) pgAdmin crashes. The crash is caused a memory access violation. Very odd. I'm using it in preference to pgAdmin II in production now and finding 200,000 row ta

Re: [pgadmin-support] pgAdmin III

Just wanted to know if you wanted reports back about bugs in pgAdmin III. I haven't seen any been reported or may be I just missed them? So i should add one: If i try to view a table with pgAdminIII (by klicking on the sunglasses or by doing a "select *" in the SQL window) pgAdmin crashes. The cra

Re: [pgadmin-support] How do you start 'library deficient' postgres

bash-2.03$ ./postmaster ld.so.1: ./postmaster: fatal: relocation error: file /usr/local/ssl/lib/libcrypto.so.0.9.6: symbol __register_frame_info: referenced symbol not found Killed It seems, you should update libcrypto (i think it's openssl) and/or recompile postgresql. by recom

[pgadmin-support] Alter Column Wizard?

possible. That one can't change column-definition is the most anoying thing about postgresql, so it would be great to overcome that problem - even if it's only with a tool like pgAdmin. Thx Sven ---(end of broadcast)--- TIP 2: you can g