Page MenuHomePhabricator

1.27.1 Installer does not connect to custom port on PostgreSQL, uses default wrong port
Closed, DuplicatePublic

Description

In 1.27.1, when using the web installer, I enter a non-default port number for the PostgreSQL database server. But when it first tries to connect to the database server to set up the schema, it ignores this and connects to the default port (5432) anyway.

If it succeeds (because I also have a database server running on the default port), then it installs the schema in the server running on port 5432, but it creates a LocalSettings.php file which includes the non-default port I entered. Which of course is missing the schema.

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

Jjanes created this task.Sep 1 2016, 8:07 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 1 2016, 8:07 PM
Aklapper renamed this task from 1.27.1 Installer connects to wrong port on PostgreSQL to 1.27.1 Installer does not connect to custom port on PostgreSQL, uses default wrong port.Sep 2 2016, 6:48 AM
Jjanes added a comment.Sep 6 2016, 9:44 PM

This was broken by change I880d4299566beaf99ed1fc21c690cdda64149b0e. It looks like PostgreSQL gets the port directly from wgDBport, by passing the Factory. Am I right that PostgreSQL is the only database that even has wiki support for non-default ports?

Jdforrester-WMF added a subscriber: Jdforrester-WMF.

Migrating from the old tracking task to a tag for PostgreSQL-related tasks.