Re: AKASH
I have been exploring an issue where pg_lsclusters reports the default port from postgresql.conf, rather than the actual port in use when a PostgreSQL cluster is started with a custom port using pg_ctlcluster (e.g., -o "-p < port>").
Can you explain why you need to use these command line options and
aren't just updating the config? This usage of pg_ctlcluster will also
bypass starting the cluster as systemd service which isn't desirable.
Christoph
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)