Closed depesz closed 2 years ago
I believe the configure flag is honored by Postgresql database and psql which is the default client that gets built as a result of the configure
command. Pgcli is a third-party client that is not going to pick up the default port that was designated at compile time. That's why we provide multiple ways to override the PORT value. Unfortunately there is nothing we can do here to automatically detect the PORT that was designated at compile time.
While I understand that detecting port might be impossible, as far as I can read python, it seems you're forcing port to be 5432 (by default) in main.py, line 1222. Perhaps if you didn't do it, and allow port to be empty, it would make libpq use the port that it was compiled with?
Description
I have custom build of Pg, with port being, by default 5430. But when i try to connect using pgcli it tries to use 5432.
Sure, I can force port using -p or PGPORT, or alias/function on pgcli, but why would a tool change default port?
Pg was compiled from sources that were configured using
./configure --with-pgport=5430
, and psql, without any options or env vars, connect to 5430.Your environment
Linux ubuntu 21.10 (impish), with Postgresql 15dev compiled from sources, on port 5430.
pip freeze: