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 1vPSy7-003JXT-36 for pgadmin-support@arkaria.postgresql.org; Sat, 29 Nov 2025 21:59:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vPSy5-00Fbmr-1L for pgadmin-support@arkaria.postgresql.org; Sat, 29 Nov 2025 21:59:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vPSy4-00Fbmj-2o for pgadmin-support@lists.postgresql.org; Sat, 29 Nov 2025 21:59:01 +0000 Received: from mail-yx1-xb12b.google.com ([2607:f8b0:4864:20::b12b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vPSy2-002Jv1-1R for pgadmin-support@lists.postgresql.org; Sat, 29 Nov 2025 21:58:59 +0000 Received: by mail-yx1-xb12b.google.com with SMTP id 956f58d0204a3-640d790d444so2334358d50.0 for ; Sat, 29 Nov 2025 13:58:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764453538; x=1765058338; 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=XOM6Nhu5uNTgXZQ7/8Xghdeuszhf9JpHZtoPeQ9hYuE=; b=OVDodc99PyBNpJDZOf6l0FdZIXB6RwFZWemzPOTQChe82Lkk1fzE4jmuBY62tnps5a 9F/nRNh9vppmVEHqq3waBredFPRQGcuzEBL2VnxZjzqDOcgayiOhDI45KjyM/cpLaLkJ zjnlcmTBcRqKhIpxlw63dry8l1pqwZOGVVzN4p+bWVR274gOYH2DzJr/kHoDMFZpWvK5 YzhLaJX1eW0M9V3V+D6Vdw/+mb9+g3DUEVkTYQSGNhaupeguDAU9LleuSP+AUkaLX+8w LrfcsbFniK2+8INYM+r+UNO4eoiiV52fbiWeMnvJZ4HxKKrA8cj37J/FQg0lD9/76NxC ie9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764453538; x=1765058338; 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=XOM6Nhu5uNTgXZQ7/8Xghdeuszhf9JpHZtoPeQ9hYuE=; b=rYoa5kR2OJzVi/dt5F9Z6kJ/A9D2AB5B4aChKZjrlIWO4mb4Z/LGwonyqR+Vgu7GXK kxuSYYYR6H42Z7NLMS8LY2e1ZWlbXhQuqskIgW4uoR8HjRB/JEt5uhs/Tvl0MRe04i9w tpn5pqEFZRSq16RA6/HjOYvZKWbEao+GUxqmnp3gf6lcq/J5t80V92TEuFAJa1NEEaE9 SMKe4g4SLHinSrTCmUUAH7z6rVKnFlhCT/uw5ZCWy1zDeIaIu/JoZ6gCFPuncWDJf890 jpa49vLi5/djidW4g7VaKcjE7RwE37K+oTXuSmmiED0mg6Lj256V2CNhdB5sHnJItGrT Aysg== X-Gm-Message-State: AOJu0Yz47ckKeYzKjRaOLrbkwuhLfk25A9lFaR4LziZlT/M8Wi5V82m+ h5ot6K9eD6KErJjzD4i5NUil3kMHk3UZ+9wPIZk6lcNntLdFca5OZVI5yXaxs9glWbuQ0vK2HJs IEhLNmxrpoOcsu8ddo3ahsUzV1J10IiE= X-Gm-Gg: ASbGncv8hBNqyTWCW9PFIFhrBtGuUsdSGwwEd6s0cJPbE1kkBvGm9/EuZ682c40CPms /RExkA2FwBiJWzDVCdmT3taUcwa2E+Ya4WayX22BA65IjGIUY37MOXoLJ24hLazcMwq03UCTURN cynFpefLZnyrlWKAMKlZcuw5NqwZQ2iY0ODv/Wr+2lWHwydA7O5LqaxzREFSx7A/moDcceXe4OG ph9/dwrNKD7PHz3KkYamDfnXJ7JuCaAJ+lR7FmOwa7z3CDvx8xv4C6GwUQyI5IeUvd1KcG3U2wk Zq1Qcry2AZATOjsIOBcN5t34ZoYc X-Google-Smtp-Source: AGHT+IG1hiAvJmipJJNYQzTbqPR1UxCndmioJpHWKqWQSASl3ycoXn49g4F63nu/HGJNnMCxTTjXfWEOrUcLCcnME0g= X-Received: by 2002:a05:690c:6d06:b0:78a:74d4:463c with SMTP id 00721157ae682-78a8b499cf1mr254038837b3.28.1764453538146; Sat, 29 Nov 2025 13:58:58 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Gus Spier Date: Sat, 29 Nov 2025 16:58:47 -0500 X-Gm-Features: AWmQ_bmxNhi042ktZYzGG8wrAkiTg4wZenQO1bzF4g9OVX7QP03nxs87087wDpE Message-ID: Subject: Re: pgAdmin4 v9.10 error -- connection failed: FATAL: database "24136" does not exist To: Dee Dockery Cc: pgadmin-support@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000005d2e920644c2da86" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005d2e920644c2da86 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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 functionalit= y > 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 psq= l. > > Any help appreciated. > --0000000000005d2e920644c2da86 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That looks suspiciously like the OID (Object Identifier) f= or a database. According to documentation, you can find the database OID wi= th
SELECT=C2=A0oid, datname FROM pg_database;<= /font>

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

That might help you.

Regards,
Gus

On Sat, Nov 29, 2025 at 11:45= =E2=80=AFAM Dee Dockery <wddocker= y@gmail.com> wrote:
This is my first pgAdmin4 post.

<= div>On my cloud server (x.x.x.x), I have been running postgres v14 for mont= hs with no problem. =C2=A0

And I have been connect= ing 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 Obj= ect Explorer, Query tool, and PSQL tool. =C2=A0

An= d I have been connecting to cloud postgres via Homebrew-installed psql on m= y local Mac with no problem.

I recently changed my postgres environm= ent:
  • updated to pgAdmin4 v9.10
  • added a postgres v17 serv= er instance on the same IP address as my cloud server, using a different po= rt
  • installed postgres v17 on my laptop so that I would have updated= psql client

Following these changes, at least briefly, I main= tained full functionality of both postgres v14 and v17 instances, full conn= ectivity via pgAdmin4 v9.10, and full connectivity via psql on my laptop.
Then, inexplicably, for the past few days, I have lost connectivity t= o postgres v14 and v17 , ONLY via pgAdmin4 v9.10 Query Tool and PSQL Tool.= =C2=A0 Connection attempt in Query Tool, for example, throws this error:
connection failed: connection to server at "xx.xx.xx.xx", po= rt 5xxx failed: FATAL: database "24136" does not exist

(No= te: =C2=A0"x" in the text above is redacted data)

"24= 136" is a mystery number. I do not have a database named "24136&q= uot;.=C2=A0 And "24136" does not appear in any field in my connec= tion 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 full connectivity to postgres v14 and v17 via laptop psql.
=
Any help appreciated.
--0000000000005d2e920644c2da86--