Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vPvrS-001x4L-1r for pgadmin-support@arkaria.postgresql.org; Mon, 01 Dec 2025 04:50:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vPvrQ-000AVD-2M for pgadmin-support@arkaria.postgresql.org; Mon, 01 Dec 2025 04:50:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vPvrQ-000AV5-1Q for pgadmin-support@lists.postgresql.org; Mon, 01 Dec 2025 04:50:04 +0000 Received: from mail-vs1-xe30.google.com ([2607:f8b0:4864:20::e30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vPvrN-002ReI-2D for pgadmin-support@lists.postgresql.org; Mon, 01 Dec 2025 04:50:03 +0000 Received: by mail-vs1-xe30.google.com with SMTP id ada2fe7eead31-5dbd2b7a7e3so2981843137.0 for ; Sun, 30 Nov 2025 20:50:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1764564599; x=1765169399; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Kyp9SUpEjBZD8GA7wJJki+JmIMmwBkTXvaJDHLmgGus=; b=ARk/zKN7MzuyoxIknk1rl3GA1bkCrDna4SGjW7qk5kkOJm8exGX0TKz2nL4Tt1gbm9 NBJncvma1EUIhbAjhEPZgniPckNrFeVw3MSb+MGlGpcf2bZolhzCpGn0flY6rbtrIC5Q 7WHsLXeqaeFKSq/qy5gmmysfZDR5Gw/BXcnWvNaPmb5uFwyRODjsMjCRH0p5r93R6gWX bq5WTZCZ7k9nSkIpa4UazodO0drTjXaPrRGBtjryjPv2bQai5QAjEAAotifCvS1n6wx1 yO1fs3f//nIU4e1I8LuFEoEoFKKrQDTmnFRjdHSFTrWllxlOn7kHBuPTpCpSFygJbEji OEeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764564599; x=1765169399; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Kyp9SUpEjBZD8GA7wJJki+JmIMmwBkTXvaJDHLmgGus=; b=n0YgQ1yc8Wa5BuOzSj+i4b2yILtci0+BmGbvrPm26lvF2be0boSnlnbJLaVQ8uqa5J WYw79JbGMjL3TJ5wmWWjQ2E+S0+fj/iZYrsi0JPKsKzOCcSIZqc/xxq+MSo6IdF5s9Mk Ax6fFOfRtnFgVPsGlm+pHTaw7h7iBH+Xv1BOTpeAbCqJ7yUCv2GdZ93jbHk+3zLTt2wx irYm1Uojqy5a+3W5LHGcobOnHgbJNiqBLg1BISI/matoWF2QbMdsMU3afseaz6zclKrE IFJaPMmSGTFgg2Whc0KXcQm9TvTbMMfqpghKCB6hV0ahPOw/92QupweEf7MRrxpbGdrx ejGg== X-Forwarded-Encrypted: i=1; AJvYcCW455Q5JGvVppwRVmKbsUG7B9NLrdZrykzxYDKZn1dQifAZgN4l0Q3+r6y0m+ERPLCNtU1ACiTPn7tzUME/1Pg=@lists.postgresql.org X-Gm-Message-State: AOJu0Yxm5fP0emp+lzlLcsO5z1eTg8aHILAIK9kakKlp5NaCluUyITEK nt24+wcbMGeBzYIfGgkxdBDuTa4Yanflcl3aI2PSoLmJhlKHmytX0+BdCC+9ImZWDboGmOttrD3 1wLRiYaBQ0fEqCNO6elKjX8p48HGXwl+mI8RUBxCv X-Gm-Gg: ASbGncsXaw3reE4eNAaMdhyRmkY9kMI55GlLUawxjMvBCpeFNuOPM5PC71MxaOj4BQM gUx9nyJs7MYO0aQHmQo+jB7wBeT6nHkMAUcsPLLso2g3W8zIBfz4KO96ILW6C4cQ8b7UjgZj4Mg sYrZhaHOLzRc5RrRWsWfSwXEPB23uE0/SfNx9SlMLCKwGg4FxaeDMXKyI2P739s4XUyrKs0KjTa HmEN5cil6NiwmmudqDSeIggYTxX7KEfy0DE3XKH4MJeZ2wXjwfLU2/PUReukJGX8RXenX5aiDmZ FBmKLDFK X-Google-Smtp-Source: AGHT+IEzgXPtwFRLI4XEowh2pFkGH6faxj3RLUBptHfJpBX93aNLrUpxsMoxse9bZ152+bQAqlMSfLZa04zfyCmkFkg= X-Received: by 2002:a05:6102:f10:b0:5db:ce1d:679f with SMTP id ada2fe7eead31-5e1de3b228cmr13483278137.26.1764564598832; Sun, 30 Nov 2025 20:49:58 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Mon, 1 Dec 2025 10:19:23 +0530 X-Gm-Features: AWmQ_bk7z1kfbBN7oTioL7S0zXihxRaJHGC4C5GSXBKQq5dEyKxDO0IFx4N4ULI Message-ID: Subject: Re: pgAdmin4 v9.10 error -- connection failed: FATAL: database "24136" does not exist To: Gus Spier Cc: Dee Dockery , pgadmin-support@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000018d0650644dcb6ae" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000018d0650644dcb6ae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Gus, This is fixed with https://github.com/pgadmin-org/pgadmin4/issues/9354 and will be available in 9.11. You can try the nightly builds - https://www.postgresql.org/ftp/pgadmin/pgadmin4/snapshots/ On Sun, Nov 30, 2025 at 3:29=E2=80=AFAM Gus Spier wro= te: > 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=E2=80=AFAM Dee Dockery wrote: > >> This is my first pgAdmin4 post. >> >> On my cloud server (x.x.x.x), I have been running postgres v14 for month= s >> 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". An= d >> "24136" does not appear in any field in my connection parameters in Quer= y >> 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. >> > --=20 Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Staff SDE II | *enterprisedb.com* "Don't Complain about Heat, Plant a TREE" --00000000000018d0650644dcb6ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Gus,

This is fixed with=C2=A0https://github.com/pgadmin-org/pgadmi= n4/issues/9354 and will be available in 9.11.
You can try the nightly b= uilds=C2=A0-=C2=A0https://www.postgresql.org/ftp/pgadmin/pgadmin4/snapshots/

On Sun, Nov 30, 2025 at 3:29=E2=80=AFAM Gus S= pier <gus.spier@gmail.com>= wrote:
That looks suspiciously like the OID (Object Identifier) for a dat= abase. According to documentation, you can find the database OID with
<= font face=3D"monospace">SELECT=C2=A0oid, datname FROM pg_database;

If that works, it will display the OID and the database name.= =C2=A0

<= div>That might help you.
=
Regards,
Gus=

On Sat, Nov 29, 2025 at 11:45=E2=80=AFAM Dee Dockery <wddockery@gmail.com= > 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 prob= lem. =C2=A0

And I have been connecting to cloud po= stgres 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, Q= uery tool, and PSQL tool. =C2=A0

And I have been c= onnecting to cloud postgres via Homebrew-installed psql on my local Mac wit= h 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
  • inst= alled postgres v17 on my laptop so that I would have updated psql client

Following these changes, at least briefly, I maintained full fun= ctionality of both postgres v14 and v17 instances, full connectivity via pg= Admin4 v9.10, and full connectivity via psql on my laptop.

Then, ine= xplicably, for the past few days, I have lost connectivity to postgres v14 = and v17 , ONLY via pgAdmin4 v9.10 Query Tool and PSQL Tool.=C2=A0 Connectio= n 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: =C2=A0"= x" in the text above is redacted data)

"24136" is a m= ystery number. I do not have a database named "24136".=C2=A0 And = "24136" does not appear in any field in my connection parameters = in Query Tool.=C2=A0=C2=A0

I still have connectivity to postgres v14= and v17 via Object Explorer in pgAdmin4 v9.10.

And I still have ful= l connectivity to postgres v14 and v17 via laptop psql.

Any help app= reciated.


--
Thanks,
Aditya Toshniw= al
pgAdmin Hacker=C2=A0| Sr. Staff SDE II=C2= =A0| enterprisedb.com
"Don't Complain about Heat, Plant a TREE"
--00000000000018d0650644dcb6ae--