| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | José António Gomes <jose(dot)antonio(dot)luanda(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL 17 Service Running but Not Listening on Network Port on Windows |
| Date: | 2025-06-18 20:51:58 |
| Message-ID: | 1179484.1750279918@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?UTF-8?B?Sm9zw6kgQW50w7NuaW8gR29tZXM=?= <jose(dot)antonio(dot)luanda(at)gmail(dot)com> writes:
> *Subject: PostgreSQL 17 Service Running but Not Listening on Network Port
> 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 accept connections
This won't immediately reveal the problem, I imagine, but it would
help decide where to look.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-06-18 21:09:03 | Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) |
| Previous Message | David G. Johnston | 2025-06-18 20:46:54 | Re: PostgreSQL 17 Service Running but Not Listening on Network Port on Windows |