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.94.2) (envelope-from ) id 1uRzlN-001rXH-IF for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Jun 2025 20:52:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uRzlJ-004sdP-Ew for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Jun 2025 20:52:02 +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.94.2) (envelope-from ) id 1uRzlJ-004sdG-69 for pgsql-bugs@lists.postgresql.org; Wed, 18 Jun 2025 20:52:01 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uRzlH-002kt4-33 for pgsql-bugs@lists.postgresql.org; Wed, 18 Jun 2025 20:52:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 55IKpwhX1179485; Wed, 18 Jun 2025 16:51:58 -0400 From: Tom Lane To: =?UTF-8?B?Sm9zw6kgQW50w7NuaW8gR29tZXM=?= cc: pgsql-bugs@lists.postgresql.org Subject: Re: PostgreSQL 17 Service Running but Not Listening on Network Port on Windows In-reply-to: References: Comments: In-reply-to =?UTF-8?B?Sm9zw6kgQW50w7NuaW8gR29tZXM=?= message dated "Wed, 18 Jun 2025 16:38:56 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1179483.1750279918.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 18 Jun 2025 16:51:58 -0400 Message-ID: <1179484.1750279918@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =3D?UTF-8?B?Sm9zw6kgQW50w7NuaW8gR29tZXM=3D?=3D writes: > *Subject: PostgreSQL 17 Service Running but Not Listening on Network Por= t > on Windows* Did you examine the postmaster log? The first few lines should show what ports it bound to. For example, on a Linux box I see 2025-06-14 12:48:07.536 EDT [12649] LOG: starting PostgreSQL 17.5 on x86_= 64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-26), = 64-bit 2025-06-14 12:48:07.536 EDT [12649] LOG: listening on IPv4 address "0.0.0= .0", port 5432 2025-06-14 12:48:07.536 EDT [12649] LOG: listening on IPv6 address "::", = port 5432 2025-06-14 12:48:07.536 EDT [12649] LOG: listening on Unix socket "/tmp/.= s.PGSQL.5432" 2025-06-14 12:48:07.543 EDT [12653] LOG: database system was shut down at= 2025-06-14 12:21:00 EDT 2025-06-14 12:48:07.554 EDT [12649] LOG: database system is ready to acce= pt connections This won't immediately reveal the problem, I imagine, but it would help decide where to look. regards, tom lane