Bugs: I suggest you Remove Postgres' future versions checking.

Open
#10,783 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
postgresql, python
Domain
databases

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

Bug

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pgadmin-org/pgadmin4

All issues in pgadmin-org/pgadmin4

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.