| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ourdiaspora <ourdiaspora(at)protonmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: php connection failure |
| Date: | 2021-08-10 13:14:33 |
| Message-ID: | 3780899.1628601273@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
ourdiaspora <ourdiaspora(at)protonmail(dot)com> writes:
> A quick ddg search revealed:
> sudo ss -tulpn
> Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
> tcp LISTEN 0 128 ::1:5432 :::* users:(("postgres",pid=21794,fd=3))
> Is the correct conclusion from this output, that the port 5432 is open?
No. The postgres process is listening, but this has nothing to do with
whether the kernel will allow any packets to arrive there.
On recent Red Hat systems, "man nft" might help you.
Not sure about other Linux variants.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2021-08-10 14:44:23 | Re: php connection failure |
| Previous Message | Matthias Apitz | 2021-08-10 09:38:57 | Re: (13.1) pg_basebackups ./. pg_verifybackup |