| From: | nonmint(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Cc: | nonmint(at)gmail(dot)com |
| Subject: | BUG #14965: PGAdmin 2.0 fails to launch after restart |
| Date: | 2017-12-11 16:51:50 |
| Message-ID: | 20171211165150.20142.79536@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 14965
Logged by: Ian Phillipchuk
Email address: nonmint(at)gmail(dot)com
PostgreSQL version: 9.6.3
Operating system: Windows 10 running on Azure VM
Description:
After installing PGAdmin 2.0 I was very pleased with the performance and new
features. Then my Azure VM I use for development shut down at the end of the
work day (as scheduled) and then I was unable to launch the application
again, it times out with "Application Server could not be contacted." I can
reinstall the application and get it to work again, but that's obviously not
a very tenable solution.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2017-12-11 20:45:38 | Re: Fwd: [BUGS] pg_trgm word_similarity inconsistencies or bug |
| Previous Message | 德哥 | 2017-12-11 15:55:35 | Re:Re: BUG #14964: statement_timeout cann't set in plpgsql |