| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | marcio(dot)elizeu(dot)ti(at)gmail(dot)com |
| Subject: | BUG #18733: Connection Timeout after upgrade |
| Date: | 2024-12-03 15:42:04 |
| Message-ID: | 18733-99d59d945ea7897d@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: 18733
Logged by: Marcio Elizeu
Email address: marcio(dot)elizeu(dot)ti(at)gmail(dot)com
PostgreSQL version: 13.16
Operating system: Linux
Description:
Connection fail with "Connection timeout expired" on pgAdmin 4 /
macOS-13.3.1-arm after upgrade from 10.22 to 13.16. I also try pgAdmin 4-8.4
and pgAdmin 4-8.12.
Access to postgres 10.22 continues to work with the same pgAdmin/macOS. The
workstations with pgAdmin/Windows access the 10.22 and 13.16 server without
any problems.
The problem seems to be linked to pgAdmin for macOS and version 13.16 of the
postgres server.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-12-03 17:02:17 | Re: BUG #18731: The psql \d command does not exactly match but can be executed |
| Previous Message | Andres Freund | 2024-12-03 15:27:41 | Re: BUG #18732: Segfault in pgbench on max_connections starvation |