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 1vPO4J-000Huj-0J for pgadmin-support@arkaria.postgresql.org; Sat, 29 Nov 2025 16:45:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vPO4G-00F3Pm-1w for pgadmin-support@arkaria.postgresql.org; Sat, 29 Nov 2025 16:45:04 +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 1vPO4G-00F3Pe-0y for pgadmin-support@lists.postgresql.org; Sat, 29 Nov 2025 16:45:04 +0000 Received: from mail-ed1-x529.google.com ([2a00:1450:4864:20::529]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vPO4E-002BD7-0Y for pgadmin-support@lists.postgresql.org; Sat, 29 Nov 2025 16:45:04 +0000 Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-640a3317b89so4294434a12.0 for ; Sat, 29 Nov 2025 08:45:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764434698; x=1765039498; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=JsrMY/IrgKUjq4yIKAQGrEiByVc0t6lSWgWZZO7El80=; b=DnukoCQnu3KwMhO1dlZCDaNDITfWMIuom/ZCvI2sFm8qokS9MmOUvKUrn8E4saElUO yNdj99JxfDPdSuRST5TbDkcTHMQw8Vwwa0u1uKQH5CCW7joa0FSQJ1q4wSGz0x+rWun2 SJzA7H+IEovqpYP+h1YkKBvQfI9xapgkc4DcnI7p/HhNBarohZxWInjdx5zFCVwSrjyn ZEdcLbvXwsCJMKRbEsCwRpxTXllE2WMpKs6TvimXM0x2hr38+eGf7eR7u8m2mhk2JfTI t+fgwa0KNtYOXOymhBLMiyrlj9XhBauN1UxtvuJh1+UrkZ86MDVfyVwqiFVtCUyAbyRT 5JjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764434698; x=1765039498; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=JsrMY/IrgKUjq4yIKAQGrEiByVc0t6lSWgWZZO7El80=; b=JaJ4YEiNzDyKcZevNJZevpQVXZTNCV6uIdZhQuJXzek/sKtDlqoz4K61SLzLyV8V8M 8+V4+nmAaJNDy7+dDwUHdHI7K2sat1kI6Sn6wUGf0ePwskwvurRy5XMmy559hD3Ltq0v 4DU4TYVi3r0VBL9k8KofCWAGUWjQdn5HCXVZpGzenUxucz7VPxTPSJmb9x1+VWroHag+ VABRkdDU8dOffJv+EoU2rHE8E9GPWqG5DDaahSFQX/JfTJg8TkREXWe9V+RuhewfYUUV IOtte0bW5zn7Jgw7V4NSHMEIeTyDExWicvUYpNiqLsgznVX4ZeimJ9sGorLH/kNGKG8w bjKQ== X-Gm-Message-State: AOJu0YzCUZ8vr3edC3bAAeMPVybw+PyPNao5z4CTlSIdmQJJpDy588YV z3HYM1ocbS4D/3vFpqS4nDmzK5C+gPMVQ055BX9dxPrs5GHAMvHe2kRM6AiuKaLHX9SKynr0dx1 6NlmWT/+aBUi27LWnmtThzEiOxdrEdPFsGnZd X-Gm-Gg: ASbGncv/SmJFRisR3vggb+SDHbBYIckeIg4I8W3xEQ/SDDfa6uH45ZSo3CKBA8BYsUx ekLEGModWRh95eY6za1gZE/yU2vWCjW4RDffOEK7ppfybhJmGp2UQvNG4B83F5g+o9kRePqjY8O LGa4tqq/MqopXokYeCw9mQ3bvVGn3mR0VPSbGUFiMyliJfAwFGPOgeDh8hllQUYE3Jyy0w/9Kl2 Z1yY/k+iRCgQyCTCQ1P7IoJ8G3wUGs+/gJs1vG0qUngnuGIyw9pzorJla7EQJf0o6RrQG0oGBsg V6dLgVk= X-Google-Smtp-Source: AGHT+IGecgj5Dm4ie9T1SJAD98fGFQNE09+JGk+sGTcY5YqTxMY+bm+TG8tcUR4m9YlgayC/6njdk7S/E9zizD92W+Q= X-Received: by 2002:a17:907:3d86:b0:b73:6c97:af4b with SMTP id a640c23a62f3a-b76c555d32cmr2125831266b.45.1764434698347; Sat, 29 Nov 2025 08:44:58 -0800 (PST) MIME-Version: 1.0 From: Dee Dockery Date: Sat, 29 Nov 2025 10:44:45 -0600 X-Gm-Features: AWmQ_bmRmGEYTERx_YB-XewA9JU4fPzOqBz_UUZo42pZKIkFn-B5gOnreUykHj0 Message-ID: Subject: pgAdmin4 v9.10 error -- connection failed: FATAL: database "24136" does not exist To: pgadmin-support@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000006ca8ef0644be77a4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006ca8ef0644be77a4 Content-Type: text/plain; charset="UTF-8" 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. --0000000000006ca8ef0644be77a4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This is my first pgAdmin4 post.

On my c= loud server (x.x.x.x), I have been running postgres v14 for months with no = problem. =C2=A0

And I have been connecting to clou= d postgres via pgAdmin4 (through v9.9) on my MacBook Air (Mac OS v15.6.1, c= hip Apple M2) for months with no problem, successfully using Object Explore= r, Query tool, and PSQL tool. =C2=A0

And I have be= en 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 clien= t

    • Following these changes, at least briefly, I maintained full= functionality of both postgres v14 and v17 instances, full connectivity vi= a 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.=C2=A0 Conne= ction attempt in Query Tool, for example, throws this error:

    connect= ion failed: connection to server at "xx.xx.xx.xx", port 5xxx fail= ed: FATAL: database "24136" does not exist

    (Note: =C2=A0&q= uot;x" in the text above is redacted data)

    "24136" is= a mystery number. I do not have a database named "24136".=C2=A0 = And "24136" does not appear in any field in my connection paramet= ers 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.
    --0000000000006ca8ef0644be77a4--