Thread: pgAdmin hangs
hi,
Regards,
Bartek
I've tried to open SQL query tool using SQL button to see table definition (Copy SQL from main window to query tool = TRUE) , but pgAdmin does not reply.
Using other instance of pgAdmin on server side, I can see new process is started for Query Tool (status <IDLE>) in server status window.
agAdmin logs:
2012-02-28 09:30:40 INFO : Opening connection with connection string: host='myHost' dbname='myDB' user='postgres' password='XXXXXX' port=5432 sslmode=require application_name='pgAdmin III - Narzędzie Zapytania'
2012-02-28 09:30:41 QUERY : Scalar query (myHost:5432): SELECT version();
2012-02-28 09:30:41 QUERY : Query result: PostgreSQL 9.1.3, compiled by Visual C++ build 1500, 64-bit
2012-02-28 09:30:41 QUERY : Set query (myHost:5432): SET DateStyle=ISO;
SET bytea_output=escape;
SELECT oid, pg_encoding_to_char(encoding) AS encoding, datlastsysoid
FROM pg_database WHERE oid = 16651
2012-02-28 09:30:41 INFO : Setting client_encoding to 'UNICODE'
2012-02-28 09:30:41 SCRIPT : Application created
server logs (server is localized to polish):
2012-02-28 09:30:40.986 CET|[nieznany]||[nieznany]|[nieznany]|2844 DZIENNIK: odebrano połączenie: host=myHost.mydomain.pl port=54269
2012-02-28 09:30:41.016 CET|[nieznany]|myHost.mydomain.pl|postgres|myDB|2844 DZIENNIK: zautoryzowano połączenie: użytkownik=postgres baza danych=myDB
2012-02-28 09:30:41.021 CET|pgAdmin III - Narz??dzie Zapytania|myHost.mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: SELECT version();
2012-02-28 09:30:41.025 CET|pgAdmin III - Narz??dzie Zapytania|myHost.mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: SET DateStyle=ISO;
SET bytea_output=escape;
SELECT oid, pg_encoding_to_char(encoding) AS encoding, datlastsysoid
FROM pg_database WHERE oid = 16651
2012-02-28 09:30:41.030 CET|pgAdmin III - Narz??dzie Zapytania|myHost.mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: set client_encoding to 'UNICODE'
I can't see nothing special in logs.
I tried to restart pgAdmin - same scenario every time, pgAdmin hangs when SQL button is clicked.
SQL pane works fine - shows table definition, problem occurs for other objects too (e.g. function, schema, operator). Strange thing for me is that this works fine on server (pgAdmin 1.14.2 on Windows Server - installed with new version of PostgreSQL)
pgAdmin 1.14.2 Windows 7 32 bit - installed outside server bundle
Server: 9.1.3 on Windows Server 2008 R2 64 bit.
Regards,
Bartek
On Tue, 2012-02-28 at 10:10 +0100, Bartosz Dmytrak wrote: > hi, > I've tried to open SQL query tool using SQL button to see table definition > (Copy SQL from main window to query tool = TRUE) , but pgAdmin does not > reply. > Using other instance of pgAdmin on server side, I can see new process is > started for Query Tool (status <IDLE>) in server status window. > > agAdmin logs: > 2012-02-28 09:30:40 INFO : Opening connection with connection string: > host='myHost' dbname='myDB' user='postgres' password='XXXXXX' port=5432 > sslmode=require application_name='pgAdmin III - Narzędzie Zapytania' > 2012-02-28 09:30:41 QUERY : Scalar query (myHost:5432): SELECT version(); > 2012-02-28 09:30:41 QUERY : Query result: PostgreSQL 9.1.3, compiled by > Visual C++ build 1500, 64-bit > 2012-02-28 09:30:41 QUERY : Set query (myHost:5432): SET DateStyle=ISO; > SET bytea_output=escape; > SELECT oid, pg_encoding_to_char(encoding) AS encoding, datlastsysoid > FROM pg_database WHERE oid = 16651 > 2012-02-28 09:30:41 INFO : Setting client_encoding to 'UNICODE' > 2012-02-28 09:30:41 SCRIPT : Application created > > server logs (server is localized to polish): > 2012-02-28 09:30:40.986 CET|[nieznany]||[nieznany]|[nieznany]|2844 > DZIENNIK: odebrano połączenie: host=myHost.mydomain.pl port=54269 > 2012-02-28 09:30:41.016 CET|[nieznany]|myHost.mydomain.pl|postgres|myDB|2844 > DZIENNIK: zautoryzowano połączenie: użytkownik=postgres baza danych=myDB > 2012-02-28 09:30:41.021 CET|pgAdmin III - Narz??dzie Zapytania|myHost. > mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: SELECT version(); > 2012-02-28 09:30:41.025 CET|pgAdmin III - Narz??dzie Zapytania|myHost. > mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: SET DateStyle=ISO; > SET bytea_output=escape; > SELECT oid, pg_encoding_to_char(encoding) AS encoding, datlastsysoid > FROM pg_database WHERE oid = 16651 > 2012-02-28 09:30:41.030 CET|pgAdmin III - Narz??dzie Zapytania|myHost. > mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: set client_encoding > to 'UNICODE' > > I can't see nothing special in logs. > I tried to restart pgAdmin - same scenario every time, pgAdmin hangs when > SQL button is clicked. > SQL pane works fine - shows table definition, problem occurs for other > objects too (e.g. function, schema, operator). Strange thing for me is that > this works fine on server (pgAdmin 1.14.2 on Windows Server - installed > with new version of PostgreSQL) > > pgAdmin 1.14.2 Windows 7 32 bit - installed outside server bundle > Server: 9.1.3 on Windows Server 2008 R2 64 bit. > It's probably because of the .pgadmin_histoqueries file. Try renaming it (don't delete it). If it works after renaming, can you send me your .pgadmin_histoqueries file? privately, if necessary (because of private queries or because it's too big). It would help me find the bug. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com
Hi,
Regards,
Bartek
works after renaming. File in different email.
Regards,
Bartek
2012/2/28 Guillaume Lelarge <guillaume@lelarge.info>
It's probably because of the .pgadmin_histoqueries file. Try renaming itOn Tue, 2012-02-28 at 10:10 +0100, Bartosz Dmytrak wrote:
> hi,
> I've tried to open SQL query tool using SQL button to see table definition
> (Copy SQL from main window to query tool = TRUE) , but pgAdmin does not
> reply.
> Using other instance of pgAdmin on server side, I can see new process is
> started for Query Tool (status <IDLE>) in server status window.
>
> agAdmin logs:
> 2012-02-28 09:30:40 INFO : Opening connection with connection string:
> host='myHost' dbname='myDB' user='postgres' password='XXXXXX' port=5432
> sslmode=require application_name='pgAdmin III - Narzędzie Zapytania'
> 2012-02-28 09:30:41 QUERY : Scalar query (myHost:5432): SELECT version();
> 2012-02-28 09:30:41 QUERY : Query result: PostgreSQL 9.1.3, compiled by
> Visual C++ build 1500, 64-bit
> 2012-02-28 09:30:41 QUERY : Set query (myHost:5432): SET DateStyle=ISO;
> SET bytea_output=escape;
> SELECT oid, pg_encoding_to_char(encoding) AS encoding, datlastsysoid
> FROM pg_database WHERE oid = 16651
> 2012-02-28 09:30:41 INFO : Setting client_encoding to 'UNICODE'
> 2012-02-28 09:30:41 SCRIPT : Application created
>
> server logs (server is localized to polish):
> 2012-02-28 09:30:40.986 CET|[nieznany]||[nieznany]|[nieznany]|2844
> DZIENNIK: odebrano połączenie: host=myHost.mydomain.pl port=54269
> 2012-02-28 09:30:41.016 CET|[nieznany]|myHost.mydomain.pl|postgres|myDB|2844
> DZIENNIK: zautoryzowano połączenie: użytkownik=postgres baza danych=myDB
> 2012-02-28 09:30:41.021 CET|pgAdmin III - Narz??dzie Zapytania|myHost.
> mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: SELECT version();
> 2012-02-28 09:30:41.025 CET|pgAdmin III - Narz??dzie Zapytania|myHost.
> mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: SET DateStyle=ISO;
> SET bytea_output=escape;
> SELECT oid, pg_encoding_to_char(encoding) AS encoding, datlastsysoid
> FROM pg_database WHERE oid = 16651
> 2012-02-28 09:30:41.030 CET|pgAdmin III - Narz??dzie Zapytania|myHost.
> mydomain.pl|postgres|myDB|2844 DZIENNIK: wyraĹĽenie: set client_encoding
> to 'UNICODE'
>
> I can't see nothing special in logs.
> I tried to restart pgAdmin - same scenario every time, pgAdmin hangs when
> SQL button is clicked.
> SQL pane works fine - shows table definition, problem occurs for other
> objects too (e.g. function, schema, operator). Strange thing for me is that
> this works fine on server (pgAdmin 1.14.2 on Windows Server - installed
> with new version of PostgreSQL)
>
> pgAdmin 1.14.2 Windows 7 32 bit - installed outside server bundle
> Server: 9.1.3 on Windows Server 2008 R2 64 bit.
>
(don't delete it). If it works after renaming, can you send me
your .pgadmin_histoqueries file? privately, if necessary (because of
private queries or because it's too big). It would help me find the bug.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
On Tue, 2012-02-28 at 12:49 +0100, Bartosz Dmytrak wrote: > Hi, > works after renaming. File in different email. > Thank you. I've found your issue. We didn't deal well with empty strings in the queries history file. It's now fixed in git. Thanks again. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com