| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | SMITH Matt <Matt(dot)SMITH(at)uk(dot)thalesgroup(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Help with PostgreSQL Upgrade |
| Date: | 2023-09-14 11:11:55 |
| Message-ID: | CE65A16A-A5B8-42F7-B7ED-551BB895CF88@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 14 Sep 2023, at 12:50, SMITH Matt <Matt(dot)SMITH(at)uk(dot)thalesgroup(dot)com> wrote:
>
> Starting the newer pgAdmin results a timeout error on the UI and the following errors in the pgAdmin log file
Are you absolutely sure you are connecting to the right instance with the right
connection parameters (hostname, port, TLS settings, etc)? If you apps and
other clients like psql can connect to the database it seems unlikely that a
pgAdmin wouldn't. It has a smell of trying to connect somewhere where nothing
is listening.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2023-09-14 14:42:36 | Re: Access plan selection logic PG9.2 -> PG14 |
| Previous Message | SMITH Matt | 2023-09-14 10:50:35 | Help with PostgreSQL Upgrade |