Control: tag -1 moreinfo

Re: wim 2019-01-15 <154755510710.20704.3906668621163200728.reportbug@zwerfkat>
> 1. connect with psql to your local instance
> 2. use alter system to set the port to a non default port
> 3. restart postgresql
> 4. you will notice that pg_lsclusters still lists the old port instead of the 
> changed port by alter system
> 5. you cannot connect with psql unless with specifying the port

Hi Wim,

this has actually been fixed in postgresql-common 170 in October 2015,
postgresql.auto.conf is now also read.

But in actual practise, there is a problem, postgresql.auto.conf is
stored inside PGDATA, which is not readable by anyone except postgres
and root, so settings modified that way are only visible (and used)
for these users.

I don't see how we can sanely get out of this problem. The idea of
connecting to the server to query pg_settings has the problem that
it's more heavyweight, and of course we need to know the port to be
able to connect... Storing the port in yet another location doesn't
seem attractive either.

Christoph

Reply via email to