That looks suspiciously like the OID (Object Identifier) for a database. According to documentation, you can find the database OID with SELECT oid, datname FROM pg_database;
If that works, it will display the OID and the database name. That might help you. Regards, Gus On Sat, Nov 29, 2025 at 11:45 AM Dee Dockery <[email protected]> wrote: > This is my first pgAdmin4 post. > > On my cloud server (x.x.x.x), I have been running postgres v14 for months > with no problem. > > And I have been connecting to cloud postgres via pgAdmin4 (through v9.9) > on my MacBook Air (Mac OS v15.6.1, chip Apple M2) for months with no > problem, successfully using Object Explorer, Query tool, and PSQL tool. > > And I have been connecting to cloud postgres via Homebrew-installed psql > on my local Mac with no problem. > > I recently changed my postgres environment: > > - updated to pgAdmin4 v9.10 > - added a postgres v17 server instance on the same IP address as my > cloud server, using a different port > - installed postgres v17 on my laptop so that I would have updated > psql client > > > Following these changes, at least briefly, I maintained full functionality > of both postgres v14 and v17 instances, full connectivity via pgAdmin4 > v9.10, and full connectivity via psql on my laptop. > > Then, inexplicably, for the past few days, I have lost connectivity to > postgres v14 and v17 , ONLY via pgAdmin4 v9.10 Query Tool and PSQL Tool. > Connection attempt in Query Tool, for example, throws this error: > > connection failed: connection to server at "xx.xx.xx.xx", port 5xxx > failed: FATAL: database "24136" does not exist > > (Note: "x" in the text above is redacted data) > > "24136" is a mystery number. I do not have a database named "24136". And > "24136" does not appear in any field in my connection parameters in Query > Tool. > > I still have connectivity to postgres v14 and v17 via Object Explorer in > pgAdmin4 v9.10. > > And I still have full connectivity to postgres v14 and v17 via laptop psql. > > Any help appreciated. >
