Hi
The netstat command did not reveal any entries on the intended port (say 5460). The 5460 port was vacant, no processes were using it.
I had to crawl through the postgres processes on task manager to find the listening port.
Could this be due interference from other services? But the port 5460 remains unused.
Regards,
Kal
On Tue, 5 Nov 2024 at 7:57 PM, Saul Perdomo <saul.perdomo@xxxxxxxxx> wrote:
" But the database actually listens on some random port like 20011"How exactly did you determine this?(If you used, say, netstat, can you share its output with us?)On Tue, Nov 5, 2024 at 8:46 AM Kal <kalel.code11@xxxxxxxxx> wrote:HiI have a scenario in which postgres listens on a random port different from the one which was specified in pg_ctl start command.This occurs in windows. When postgres is started on port 5460, the logs denote that postgres is started on 5460. But the database actually listens on some random port like 20011When the same postgres is started as a service,it listens on the intended port.I have tried with both normal and admin users.Any suggestions on this behaviour will be helpful.RegardsKal
