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 1vQI9V-00491l-2N for pgadmin-support@arkaria.postgresql.org; Tue, 02 Dec 2025 04:38:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vQI9U-005bcV-1L for pgadmin-support@arkaria.postgresql.org; Tue, 02 Dec 2025 04:38:12 +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 1vQI9U-005bcN-0V for pgadmin-support@lists.postgresql.org; Tue, 02 Dec 2025 04:38:12 +0000 Received: from mail-ua1-x92e.google.com ([2607:f8b0:4864:20::92e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vQI9Q-002faZ-2K for pgadmin-support@lists.postgresql.org; Tue, 02 Dec 2025 04:38:11 +0000 Received: by mail-ua1-x92e.google.com with SMTP id a1e0cc1a2514c-93a9f6efe8bso1172271241.0 for ; Mon, 01 Dec 2025 20:38:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1764650286; x=1765255086; 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=dQrXGJZo9Ab3zhSAIpCHijWsA8wChBg1PCH6a6F2ekM=; b=bUPVnChH+KS+kLc8gv3cK25DgaRYjYRDeXDsh6ooSHt46HrlFbbECrypKal2Kq9E+l eACNPJKzfLfBjghWmU/LZuTBy2AaBFpajxzU6uMastxcOhmXyVvDpnmnppuhDYLxXwjq KmBO2Pva35M9G529m9dzCkjaoQ26B+k8Yrjdc+iUgsmcYCVnEZMfAN3tdewduQxg1g8V NebvRQfPVoJ1EwqAEqpfbcEKZt6XXkh4k1AiXOstttnq8Etw7xlNFJHZJ7pGkzgDuYrY HhD1g6goO8v/x6gxgyuJZxw2jMTcib2YouMmi03iGcOGtoWqKMp53JFAIxx48kOB9seo DquQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764650286; x=1765255086; 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=dQrXGJZo9Ab3zhSAIpCHijWsA8wChBg1PCH6a6F2ekM=; b=KEsZ+c2arl4HOAKxxacIX9WKKubRrqvEEQuVWsN3wUNXE0Wj+3dTN/9Ad+wpNzANlo 3KxEdEW/nQfAUuz6XzK23fGuQJJ4NLVYyZTxrLbZnWBHO2CK4dqRe3hNGVS/PoEHIyCx aPdKycSWuoOFX/OzM0NlzFLCvB69T9WWNULB/D/gEyYOzsffljFN0ZSNxsGeDdiDtYFH oCawPXZW36UMKeYrmrDwm1Av1rnsX3p+MLJkOVvjjG/DcKFogf+o1jZOYL8C5KWGpdCB z8OWCFQEZ/r7lu5gBDcoRNRH5v7uPD7eadV75uMqNPo0d07vPgIeuyn4tBu8/dqhECe6 xZFQ== X-Forwarded-Encrypted: i=1; AJvYcCU/FvtsqNj5WmfSydsi0gMz/rndSpTqEUkJvAjItfSqK5GPxwmRBJ5ppQwZj3r5OmZgvrI8RFH4cpNxSNDz2OU=@lists.postgresql.org X-Gm-Message-State: AOJu0Yx02FT+3fyTO9R8vhgj24UIiytVkrgBBdhTelKFw9QwL15OHXQs 9HT6GwpVTT1r7Q8MB2LfocmSA7ZetQZjkpl8i6WD1ueMPVBN9nbk685Y+mdXVJCOLYfGfjGs8sL wfIWzyY72n9M3GtQkJHRRPVcJI2U7PBf5ViPO+blaTNHJyQpg6d0= X-Gm-Gg: ASbGncuKeFa6EyyE4V3soZgIW0CFsPLmLHwjpvOHJxkrW+s3SM4EO6RFh6EI4B9le22 Top8JulDIgd1H2i4Vpoq0KPA2RyyXK+oqdm+zMvHiC2NpJEDY3bLHsQi+DE1ORteskzq2/ghc63 1U3OSxg36bQFbj7B2xUTFe9UxlwdOIE4cp034qpYQMLWJXy7eNHhWTmfR/CYyLRGd/0XMoKNUdc 1EUN6Zl/RUh7kWpJgjh8NwpgXNatlrdy7mEK4oiDe91x72JdtE1Q/qp6YxbIz0mm7LpDpBFtw== X-Google-Smtp-Source: AGHT+IFaK1Ln1ugK0H8Z8zGQvTY02UUggemasJPbOhjDEzgssggQWNUZuIMZGrETHRAXBBTYCGHkJEOGpg4ypq5EtaE= X-Received: by 2002:a05:6102:5e84:b0:5dd:83de:badc with SMTP id ada2fe7eead31-5e1de4050c3mr13861116137.38.1764650285784; Mon, 01 Dec 2025 20:38:05 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Tue, 2 Dec 2025 10:07:29 +0530 X-Gm-Features: AWmQ_bnxg-0csITa6eGFyoKuBKbp8TMayvQMnH-GJOFg1MiTpYVs7LGwfNVdwGc Message-ID: Subject: Re: pgAdmin4 v9.10 error -- connection failed: FATAL: database "24136" does not exist To: Dee Dockery Cc: Gus Spier , pgadmin-support@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000006ff0dd0644f0a922" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006ff0dd0644f0a922 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Dee, It is scheduled to be released on 11th Dec if everything goes well. On Tue, Dec 2, 2025 at 2:28=E2=80=AFAM Dee Dockery wr= ote: > 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 > 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 = wrote: > >> > >> 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 n= o > 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 v= ia > 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. > 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. > > > > > > > > -- > > Thanks, > > Aditya Toshniwal > > pgAdmin Hacker | Sr. Staff SDE II | enterprisedb.com > > "Don't Complain about Heat, Plant a TREE" > --=20 Thanks, Aditya Toshniwal pgAdmin Hacker | Sr. Staff SDE II | *enterprisedb.com* "Don't Complain about Heat, Plant a TREE" --0000000000006ff0dd0644f0a922 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Dee,

It is scheduled to be released on 11th Dec if= everything=C2=A0goes well.

On Tue, Dec 2, 2025 = at 2:28=E2=80=AFAM Dee Dockery <w= ddockery@gmail.com> wrote:
Hi, Aditya.=C2=A0 Thanks for clarifying that this is a kn= own issue.

I don't normally download nightly builds.=C2=A0 Can you predict when 9.= 11
will become available?

William

On Sun, Nov 30, 2025 at 10:49=E2=80=AFPM Aditya Toshniwal
<= aditya.toshniwal@enterprisedb.com> wrote:
>
> Hi Gus,
>
> This is fixed with https://github.com/pgadmi= n-org/pgadmin4/issues/9354 and will be available in 9.11.
> You can try the nightly builds - http= s://www.postgresql.org/ftp/pgadmin/pgadmin4/snapshots/
>
> On Sun, Nov 30, 2025 at 3:29=E2=80=AFAM Gus Spier <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
>> 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 <wddockery@gmail.com&g= t; 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 (thr= ough v9.9) on my MacBook Air (Mac OS v15.6.1, chip Apple M2) for months wit= h no problem, successfully using Object Explorer, Query tool, and PSQL tool= .
>>>
>>> And I have been connecting to cloud postgres via Homebrew-inst= alled 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 updat= ed psql client
>>>
>>>
>>> Following these changes, at least briefly, I maintained full f= unctionality 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 connect= ivity to 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 err= or:
>>>
>>> connection failed: connection to server at "xx.xx.xx.xx&q= uot;, port 5xxx failed: FATAL: database "24136" does not exist >>>
>>> (Note:=C2=A0 "x" in the text above is redacted data)=
>>>
>>> "24136" is a mystery number. I do not have a databas= e named "24136".=C2=A0 And "24136" does not appear in a= ny field in my connection parameters in Query Tool.
>>>
>>> I still have connectivity to postgres v14 and v17 via Object E= xplorer in pgAdmin4 v9.10.
>>>
>>> And I still have full connectivity to postgres v14 and v17 via= laptop psql.
>>>
>>> Any help appreciated.
>
>
>
> --
> Thanks,
> Aditya Toshniwal
> pgAdmin Hacker | Sr. Staff SDE II | enterprisedb.com
> "Don't Complain about Heat, Plant a TREE"


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