pgAgent does not start with message “ERROR: Couldn't register event handle.”

2018-05-17 Thread Arturas Mazeika
Dear postgres Folk, I am able to start the pgAgent in debug mode on a windows (server 2016) machine with the help of C:\Program Files (x86)\pgAgent\bin>pgagent.exe DEBUG "host=localhost port=5432 user=postgres dbname=postgres password=" I also tested that I can start jobs through pgA

Re: SQL_ASCII support (or lack thereof)

2018-05-17 Thread richard coleman
Dave, Thanks for getting back to me on this issue. If this is the case then it would seem that using python for pgAdmin4 development was a poor choice considering the fact that PostgreSQL 10 supports more than two dozen types of encoding, only one of which is UTF8. In my case I have a SQL_ASCII

Re: Error on accessing SQL tab for triggers

2018-05-17 Thread Murtuza Zabuawala
This bug was found just after we release pgAdmin4 v3.0 but we have fixed it now and it should resolve the issue with next release. Ref: https://redmine.postgresql.org/issues/3179 -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Thu, May

Re: SQL_ASCII support (or lack thereof)

2018-05-17 Thread Dave Page
On Thu, May 17, 2018 at 3:06 PM, richard coleman < rcoleman.ascen...@gmail.com> wrote: > Why is pgAdmin 4 so hostile to SQL_ASCII databases? > > We have several production databases dating back to 9.1 that are SQL_ASCII > encoding but in pgAdmin4 I am constantly having to *clean up* non *UTF8* dat

SQL_ASCII support (or lack thereof)

2018-05-17 Thread richard coleman
Why is pgAdmin 4 so hostile to SQL_ASCII databases? We have several production databases dating back to 9.1 that are SQL_ASCII encoding but in pgAdmin4 I am constantly having to *clean up* non *UTF8* data. The same data works just fine in the pgAdmin3 series. Running the same query in psql yields

Error on accessing SQL tab for triggers

2018-05-17 Thread McDonaldR
Hi List I've comes across an error when trying to access my triggers through pgAdmin 4 v3.0. Maybe you can point me in the right direction for a solution? Expanding the tree down through database > schemas > schema > trigger functions > trigger returns: Error retrieving the information - INT

Re: Query Tool Initialization Error

2018-05-17 Thread Chris Cowan
Ok, will do, but will be late today (UK time). Chris sent from iPhone From: Murtuza Zabuawala Sent: Thursday, May 17, 2018 9:13:57 AM To: Chris Cowan Cc: pgAdmin Support Subject: Re: Query Tool Initialization Error Hi, Could you provide more details like, - Wha

Re: Query Tool Initialization Error

2018-05-17 Thread Jan Birk
Hi, I have seen the same error when renaming the alias. In /etc/httpd/conf.d/pgadmin4-30.conf renaming the alias from: WSGIScriptAlias /pgadmin4-30 /usr/lib/python2.7/site-packages/pgadmin4-30-web/pgAdmin4.wsgi to WSGIScriptAlias /pgadmin4 /usr/lib/python2.7/site-packages/pgadmin4-30-web/

Re: Query Tool Initialization Error

2018-05-17 Thread Murtuza Zabuawala
Hi, Could you provide more details like, - What is your pgAdmin4 version? - How did you installed it? - On which OS you are trying to run pgAdmin4? - Could you please provide pgAdmin4.log file with debug mode on. For more information check: https://www.pgadmin.org/faq/#8 (Rename/delete your previ

Query Tool Initialization Error

2018-05-17 Thread Chris Cowan
I have encountered a problem with loading the Query Tool with Postgres 10 and 9.6. I have uninstalled/reinstalled and tried different versions, but I am unable to clear this problem. Unless there is a known solution I will need to switch to another db. Let me know if this is a known problem with