Agreed - it sounds like OP found a *client *process and mistook it for a server process, which is why I wanted to know where exactly he saw this.
On Tue, Nov 5, 2024 at 9:41 AM Ron Johnson <ronljohnso...@gmail.com> wrote: > On Tue, Nov 5, 2024 at 9:22 AM Kal <kalel.cod...@gmail.com> wrote: > >> >> On Tue, 5 Nov 2024 at 7:42 PM, Greg Sabino Mullane <htamf...@gmail.com> >> wrote: >> >>> Start by seeing where the port is actually being set by running this: >>> >>> select setting, source, sourcefile, sourceline from pg_settings where >>> name = 'port'; >>> Cheers, >>> Greg >>> >>> Hi Greg, >> >> The query output states the source as command line. Event the port value >> output from show port is same as given in pg_ctl command. >> >> But the database is listening on some other random port. >> > > *Client* applications use a random port on *their* host: In this case, > 10.176.242.216 is the client, and 10.109.165.4, and 10.176.252.201 are > the DB servers: > > $ netstat -an | grep :5432 > tcp 0 0 10.176.242.216:37086 10.109.165.4:5432 > ESTABLISHED > tcp 0 0 10.176.242.216:43256 10.176.252.201:5432 > TIME_WAIT > tcp 0 0 10.176.242.216:36172 10.143.170.55:5432 > TIME_WAIT > tcp 0 0 10.176.242.216:36142 10.143.170.55:5432 > TIME_WAIT > tcp 0 0 10.176.242.216:36156 10.143.170.55:5432 > TIME_WAIT > tcp 0 0 10.176.242.216:36174 10.143.170.55:5432 > TIME_WAIT > tcp 0 0 10.176.242.216:38998 10.109.165.4:5432 > TIME_WAIT > tcp 0 0 10.176.242.216:36186 10.143.170.55:5432 > TIME_WAIT > tcp 0 0 10.176.242.216:36188 10.143.170.55:5432 > ESTABLISHED > tcp 19 0 10.176.242.216:36196 10.143.170.55:5432 > ESTABLISHED > tcp 19 0 10.176.242.216:36208 10.143.170.55:5432 > ESTABLISHED > tcp 0 0 10.176.242.216:36210 10.143.170.55:5432 > ESTABLISHED > > -- > Death to <Redacted>, and butter sauce. > Don't boil me, I'm still alive. > <Redacted> crustacean! >
