Add configuration option for postgres port #3097
-
The Postgres port I propose to add a variable |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
Can you explain your exact use case? Do you want to use the manual-install method and use an external postgres database in there? Also why arent you able to use the default port? |
Beta Was this translation helpful? Give feedback.
-
We use a centralised multi-replica fail-over PG cluster for all services we host. This ensures HA on the PG side, less admin overhead than one for each service, and better resource usage than one for each service. Failover connections and distribution to the current primary are handled via a pgbouncer, which in our installation listens on another port than the default pg port.
See above, though I wasn't directly involved in the whole planning, my understanding is that we plan on using AIO with our own Postgres. If that is only supported on manual-install that will probably be what is planned, yes.
The short answer is because it's configured this way and changing it would mean rearchitecting parts of our setup. We understand adding a configuration option is also devoid of work, we'd be willing to have a crack at a PR if there's interest in this feature. (I also had a little longer and snarkier answer, it would probably not bring things forward, so not for today) |
Beta Was this translation helpful? Give feedback.
-
Hardcoding the port is a bad idea, and also ignoring the conf.php settings is a problem: nextcloud/server#45496 |
Beta Was this translation helpful? Give feedback.
The dbport can be adjusted since a while now: #4433