From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Nigel Tucker <nigel(at)specialisedstructures(dot)co(dot)nz> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: PgAdmin 4 not working in Windows 10 |
Date: | 2016-10-03 09:17:44 |
Message-ID: | CA+OCxow4RNT1VZy3PQpZTpXq1fb6mvN978oVwr3bBsU8x0LcLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi
On Sat, Oct 1, 2016 at 6:13 PM, Nigel Tucker <
nigel(at)specialisedstructures(dot)co(dot)nz> wrote:
> Hi,
>
>
>
> I have recently installed the new Postgres 9.6 RC1, having previously used
> 9.2, 9.4, and 9.5 extensively for all our business activities.
>
>
>
> As a test, I performed a pg_upgrade to create a new copy of several
> databases on 9.6 RC1. All fine.
>
>
>
> However PgAdmin 4 always crashed with the usual ‘PgAdmin stopped working’
> message that it has always been prone to – but this time whenever I try to
> open ANY database.
>
I'm not aware that it's always been prone to that. I've seen one or two
reports, but that was amongst over 500 issues during development..
>
>
> I spent several hours installed Python in case it needed that to run
> correctly, and this seemed to improve things – it now crashes only every 10
> minutes or so. But now it’s gone back to crashing whenever I open a
> database again.
>
Unless you've modified the config options, then installing Python won't
make any difference. The runtime itself (which is the bit that would give
the message above) is written in C++, and is linked with the Python
interpreter at build time.
>
>
> So Question 1: Where is the pg_admin log now being stored if anywhere – if
> not, where can I set its path so I can see what’s happening?
>
Under the %AppData% directory,
e.g. C:\Users\dpage\AppData\Roaming\pgAdmin\pgadmin.log. You can change
that in config_local.py (see config.py for the default setting, which you
can copy/paste into config_local.py to override).
Note that that is the log for the application server, i.e the Python code
that is hosted in the runtime. The runtime doesn't have it's own log,
besides what you might find in the event viewer.
> Question 2 – why doesn’t pgAdmin 4 for windows 10 work?
>
It does for thousands of other people (at least we assume it does - they're
keeping quiet if it doesn't). Of course there are always exceptions where
some unexpected environmental issue causes problems.
>
>
> Since we use the Express for Windows Desktop version of Visual Studio
> 2015, the path to the debugger seems unavailable – have you any suggestions
> how to find out what is going wrong?
>
It does sound like a runtime issue. You could install Qt, then try
compiling/debugging your own build of the runtime. I'd hold on that option
for the moment though, as it can take a little effort to setup a build
environment.
Before you do anything else though, please make sure you upgrade to
PostgreSQL 9.6.0 and pgAdmin 4 1.0 (i.e. the GA versions, not RC1).
>
>
> I am happy to return to 9.5 for the moment, but I was really looking
> forward to using the new interface, and implementing it for all our users
> across the country.
>
>
>
> Sadly,
>
>
>
> Nigel
>
>
>
> *Dr Nigel Tucker*
>
> System Architect
>
> Specialised Structures NZ
>
> Telephone Direct (NZ) +64 (0) 3 482 2473
>
>
>
> [image: SS with Custom]
>
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Rössler | 2016-10-03 09:57:34 | Re: pgAdmin4 - Query Tool stuck "Initializing the query execution!" on localhost |
Previous Message | Dave Page | 2016-10-03 09:06:06 | Re: Cannot launch pgAdmin4 |