I opened this issue at pgAdmin tree view doesn't show all databases from YugabyteDB Cloud · Issue #10186 · pgadmin-org/pgadmin4 · GitHub and have reposted it here.
I am able to query data from YugabyteDB cloud cluster but the database is not displaying correctly in pgAdmin. I attached two screenshots of my pgAdmin browser.
Describe the bug
pgAdmin’s tree view only displays the postgres database when connected to YugabyteDB Cloud, even though the connection is correctly configured with yugabyte as the maintenance database. SQL queries prove that all databases exist and are accessible, but they don’t appear in the tree view.
To Reproduce
Steps to reproduce the behavior:
- Connect to YugabyteDB Cloud (Aeon) cluster
- Configure connection with:
- Maintenance database:
yugabyte - SSL Mode: Verify-Full
- Root certificate: YugabyteDB CA certificate
- Maintenance database:
- Expand the server in tree view
- Expand “Databases” folder
- Observe that only
postgresdatabase is shown
Expected behavior
Tree view should display all 3 databases: postgres, yugabyte, system_platform
Error message
No error messages. The connection succeeds, but databases are missing from the tree view.
Evidence this is a pgAdmin UI bug (not database issue):
- SQL query confirms all databases exist and are accessible:
SELECT datname FROM pg_database WHERE datistemplate = false;
Returns: postgres, yugabyte, system_platform
- Queries against the
yugabytedatabase work perfectly:
SELECT COUNT(*) FROM awdc.laas_population_data;
Returns: 59,153 rows (proves connection to yugabyte database works)
- Connection settings verified correct:
- Maintenance database:
yugabyte(NOTpostgres) - Query Tool connects to correct database
- All credentials confirmed working
- Maintenance database:
Screenshots
Desktop (please complete the following information):
- OS: Windows 11
- pgAdmin version: 9.8
- Mode: Desktop
- Package type: Windows installer
Additional context
- Database: YugabyteDB Cloud (Aeon)
- The
yugabyteandsystem_platformdatabases are accessible via Query Tool - This affects teams who rely on visual tree navigation to explore database schemas
- Current workaround: Use Query Tool exclusively for all database operations

