psql ignores server port setting through alter system when connecting?

From: Wim Bertels <wim(dot)bertels(at)ucll(dot)be>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: psql ignores server port setting through alter system when connecting?
Date: 2017-11-17 11:04:22
Message-ID: 7d92073a-524c-2bad-af9c-0e00256619a4@ucll.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hallo,

i tested this on two debian stable machines with the apt.postgresql.org
repo enabled. Can anyone confirm this?

Version: 10.1-1.pgdg90+1

Steps to reproduce

1. connect to your db using a unix socket, for example
$ psql --cluster 10/main postgres

2. change the port with alter system, for example
# ALTER SYSTEM set port TO 54331;

3. restart the cluster
# pg_ctlcluster 10 main restart

4. check
# pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
9.6 main 5432 online postgres /var/lib/postgresql/9.6/main
/var/log/postgresql/postgresql-9.6-main.log
10 main 54331 online postgres /var/lib/postgresql/10/main
/var/log/postgresql/postgresql-10-main.log

5. try to connect again as in 1.
$ psql --cluster 10/main postgres
psql: could not connect to server: Bestand of map bestaat niet
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5433"?

6. check again
$ ss -a | grep 5433
u_str LISTEN 0 128 /var/run/postgresql/.s.PGSQL.54331
554855 * 0
tcp LISTEN 0 128 127.0.0.1:54331 *:*

tcp LISTEN 0 128 ::1:54331 :::*

Background:
The port in postmaster.conf was always 5433 in this test case, also a
non standard port to try to pinpoint the problem closer.

hth,
Wim

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message sagadin 2017-11-17 11:26:00 BUG #14917: process hang on create index
Previous Message Amit Kapila 2017-11-17 07:51:07 Re: 10.1: hash index size exploding on vacuum full analyze