From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | ed(dot)g(at)earthlink(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16392: Unable to logon |
Date: | 2020-04-27 00:46:06 |
Message-ID: | 20200427004606.GA21731@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, Apr 26, 2020 at 10:12:12PM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16392
> Logged by: Ed Grochowski
> Email address: ed(dot)g(at)earthlink(dot)net
> PostgreSQL version: 12.2
> Operating system: Windows 10
> Description:
>
> I am running a synology server with the bundled PostgreSQL. I have modified
> the configuration to allow it's use as a networkes database. I do
> development locally on MAC OS Sierra and Windows 10 and the Synology.
> Here is the problem: I can access Postgres on Synology with pgAdmin4 thruogh
> ssh from Win 10 and Mac until I install postgres locally on Windows. pgAdmin
> onn the Mac has no trouble connecting to the Synology db but Windows
> initially connects to the server but quicly drops the connection. I have
> installed pgAdmin separately and bundled with no difference. When pgAdmin is
> running without postgres locally everything works fine. When I reinstall
> Postgres and connect to the local database pgAdmin drops the network
> version.
> This seems like a pgAdmin4 configuration issue but I can't pin it down. I
> have tried other versions of pgAdmin4 with the same results. It is not a
> database issue but a pgAdmin on Windows 10 issue as again, it works fine on
> the Mac.
For PGAdmin support, see:
https://www.pgadmin.org/support/list/
or email
pgadmin-support(at)postgresql(dot)org
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-04-27 00:53:35 | Re: BUG #16272: Index expression can refer to wrong attributes if index is created via CREATE TABLE LIKE |
Previous Message | PG Bug reporting form | 2020-04-26 22:12:12 | BUG #16392: Unable to logon |