Bugs: I suggest you Remove Postgres' future versions checking.
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by locating the PostgreSQL version check used when pgAdmin opens an SSH tunnel connection, then compare how it handles PostgreSQL 19 RC1 and RC2. Reproduce the reported connection failure with RC2 and check whether the version check causes it. Done means pgAdmin can connect through the tunnel to RC2 without removing compatibility checks that other versions depend on.
Written by the indexing model from the issue text.
Description
I am using pgAdmin 4.19 , Postgres 19 RC2 via SSH tunnel. I cannot connect.
I am using pgAdmin 4.19 , Postgres 19 RC1 via SSH tunnel. I can connect.
I am using Navicat via SSH tunnet. I can connect success.
Please remove future Postgres versions checking in pgadmin.
The PostgreSQL server is not bound to 0.0.0.0 as initially believed; it's listening on 127.0.0.1:5432 with established connections. The tunnel is running and listening, which indicates a local access setup. The error points to a version incompatibility within the pgAdmin setup, not the database configuration.
The pgAdmin 4 traceback indicates a version parsing error, specifically failing to convert 'None' to an integer. This occurs because the pgAdmin 4 version likely doesn't support the PostgreSQL version being connected to, which is likely a newer version like 19. The mismatch in version is causing the parse failure within the versioned_template_loader.py file.
- Dominant language
- Python
- Stars
- 3.9k
- Forks
- 922
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 33
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pgadmin-org/pgadmin4
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pgadmin-org/pgadmin4#10797 ·
Maintainers usually reply within 2 days
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pgadmin-org/pgadmin4#10426 · 3 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
pgadmin-org/pgadmin4#10796 · 1 comment ·
Maintainers usually reply within 2 days
-
Schema Diff does not detect foreign keys that reference a different schemaPossibly taken @dpage claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 57/100
pgadmin-org/pgadmin4#10786 · 1 assignee ·
Maintainers usually reply within 2 days
-
pgAdmin 4 v9.19 - Application freezes when interacting with the UIPossibly taken @CoderKing2705 claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pgadmin-org/pgadmin4#10767 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
All issues in pgadmin-org/pgadmin4
Similar issues
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ida-arbeitszeit/workers-control#1588 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
aws-samples/sample-per-model-bedrock#930 ·
Maintainers usually reply within 1 day
-
Locus / Transcript lacks __bool__, so bool(transcript) queries the SQLite exon table via __len__Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
awslabs/visual-asset-management-system#1646 ·
Maintainers usually reply within 1 day