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 1vQAyD-000ikn-20 for pgadmin-support@arkaria.postgresql.org; Mon, 01 Dec 2025 20:58: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 1vQAyC-004Pf4-0k for pgadmin-support@arkaria.postgresql.org; Mon, 01 Dec 2025 20:58:04 +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 1vQAyB-004Pev-2n for pgadmin-support@lists.postgresql.org; Mon, 01 Dec 2025 20:58:04 +0000 Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vQAy9-002dMl-0d for pgadmin-support@lists.postgresql.org; Mon, 01 Dec 2025 20:58:03 +0000 Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-640c6577120so8350572a12.1 for ; Mon, 01 Dec 2025 12:58:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764622680; x=1765227480; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=W/zGod/1sfZDez4IIoMlnn4i0F37HUpiJZuC7t7w1kQ=; b=PY+Ecmcgfv7CXRC5MC74ByHPBpntHX4JPpNndbx8ljyS6S/xmhf7cAdujtmX9MKOXp 3UtwMMuvVZcGFu9tBP4iBj71jJBSJLCTBByJukTgtGgy7rGwiDKJrkS/YezCOcrVBQDY yYmRF42wmyOi88GuGOtKrR2xaISt6RMACflvUKcPKxcLNmDboXZja7r74aetra6F6doM 9fPguCSqjEgAEzr4hqqSPoaPtrs8IyOkpTEzBrai+zvKWZHsAyCbub5ca+N7rbA9KUp0 BE9kTryBFmQ3OHEv76HVbKfR5QRPqA5Tddu/2/zZaCa0RH8EXm+CAacL7iKASxGMTof1 Za6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764622680; x=1765227480; h=content-transfer-encoding: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=W/zGod/1sfZDez4IIoMlnn4i0F37HUpiJZuC7t7w1kQ=; b=Nurh1wWDb8bwpNi54zAHrN4/jm3CzKtCBHETTns5vdy+P0Ymbj+OyELs3fknQecFPG H5P3Ce+66Wx0P3MyrxLlvkHFrTLop8DOKTURnRvQiX9gkLDgveylA9NNeClKLamaCbdb tAycU8DOdjhWJ0+W6jP38SM1GlAtrdEoCrOm6sHVQ5iMRj2tFEQgU7RMeLuxCRGubcDv IlEALU0s4TH+IROXKazsM0licvgW6gha/3qbeENgqdwZGZ+NuzmDUNqqBrAzKf0Qj0kQ GJaGAe0b9res/rPrnjh19TMLLZLHWbSATVxeIy3g79Q6gYWB9QwFfH7O/4NdKaI7pgaz bIQg== X-Forwarded-Encrypted: i=1; AJvYcCUoWg6ZNe2OlmNDtBE23vvTpRkZsG9xvq/C6M561ejcFLXA3rEykx+xIw4HOebMPytANZxeTTXAPe5KBNTsMZk=@lists.postgresql.org X-Gm-Message-State: AOJu0YyYRf7gNRc43rACPL8qY0Im6k9ul7rNCHtbzu/3D5NvksuB3cWu vNww8sK3bXWanD8BVyFAf1//bSjUJ0OWN3eTCk92G/1cDMcTwwaH2jiFHBPFp47qmRaFtK8R38A tqFkOm2NpCrNKGr8KXnSH9PlrD9w6E9k= X-Gm-Gg: ASbGncv8IazFr0Gmr+ct7hvfc6GUb2FAtE9pv/qA9DTKaU60F2pSMMfzith7ieWWPmK GNtMegRThU/PPHhSaFIx3FLvCU2nmpIsOPhWCr1Tms4HCeP90F6ro/8uvZE7UI4VBCzwfUqWERa v6K5cBJJvkYj5d9HpY0mLCD+yTgp0A+/Kf18Mi6Fl7rLhzRJnZRo5JJqQR2In/SbO+7K8JQItsx 1kZOZsmDvG7j+/pBi8FGpajuzXuF7lqTO8FaJxfZmefRDWy9YNZrgzQ41QWJHs43hPbefGCvoll LRSz X-Google-Smtp-Source: AGHT+IGGqMPGIZ9o022zE+SmIy6z0oV/mG/3Bjkh9DOEcEW+Ai2kx+mxXUods8hAf2H/tgL5Kctx9aDt257qEXweHEU= X-Received: by 2002:a17:907:969e:b0:b73:6f8c:6100 with SMTP id a640c23a62f3a-b767170a3c0mr3596404466b.39.1764622679843; Mon, 01 Dec 2025 12:57:59 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dee Dockery Date: Mon, 1 Dec 2025 14:57:47 -0600 X-Gm-Features: AWmQ_bkX5EPXZ1oYpsItLZnkjiRZBe_q1cPt2ri5CF2DQ4ybiosB1HlyKiGn1jc Message-ID: Subject: Re: pgAdmin4 v9.10 error -- connection failed: FATAL: database "24136" does not exist To: Aditya Toshniwal Cc: Gus Spier , pgadmin-support@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, Aditya. Thanks for clarifying that this is a known issue. I don't normally download nightly builds. Can you predict when 9.11 will become available? William On Sun, Nov 30, 2025 at 10:49=E2=80=AFPM Aditya Toshniwal wrote: > > Hi Gus, > > This is fixed with https://github.com/pgadmin-org/pgadmin4/issues/9354 an= d will be available in 9.11. > You can try the nightly builds - https://www.postgresql.org/ftp/pgadmin/p= gadmin4/snapshots/ > > On Sun, Nov 30, 2025 at 3:29=E2=80=AFAM Gus Spier w= rote: >> >> 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 mont= hs 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 prob= lem, successfully using Object Explorer, Query tool, and PSQL tool. >>> >>> And I have been connecting to cloud postgres via Homebrew-installed psq= l 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 c= lient >>> >>> >>> Following these changes, at least briefly, I maintained full functional= ity 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. C= onnection attempt in Query Tool, for example, throws this error: >>> >>> connection failed: connection to server at "xx.xx.xx.xx", port 5xxx fai= led: 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". A= nd "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 i= n pgAdmin4 v9.10. >>> >>> And I still have full connectivity to postgres v14 and v17 via laptop p= sql. >>> >>> Any help appreciated. > > > > -- > Thanks, > Aditya Toshniwal > pgAdmin Hacker | Sr. Staff SDE II | enterprisedb.com > "Don't Complain about Heat, Plant a TREE"