Thank you for your response. You raise a valid point about updating the
config file instead of using command-line options.
One genuine use case we encounter is during database failover testing and
recovery drills. We need to temporarily spin up secondary instances of
existing clusters on different
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 comm
Package:postgresql-common
Verison:273.pgdg24.04+1
*Dear Community,*
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
3 matches
Mail list logo
