Glom suggests postgresql-8.2, but doesn't use the right port.

Bug #86582 reported by Andrew Ruthven
2
Affects Status Importance Assigned to Milestone
glom (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: glom

Package: glom
Version: 1.3.8-0ubuntu1
Severity: normal

Glom suggests postgresql-8.2 which listens on port 5434 by default.
When Glom attempts to connect to the PostgreSQL database it tries
ports 5432 and 5433, but *not* 5434.

Unfortunately I don't see any way to tell Glom to use a different port
via the Database specification dialog. It looks like the standard
of using "<hostname>:<port>" doesn't work.

While I could (and will) change the port that PostgreSQL 8.2 uses, I don't
think that is the correct long-term solution. Glom should really try port
5434 now as well...

Revision history for this message
Murray Cumming (murrayc) wrote :

I'll add that to the list of hard-coded ports for the next release, plus some more in this sequence for the future. Ideally, postgresql should use avahi on Linux, as it already uses Bonjour on MacOS X, to advertise itself.

Revision history for this message
Murray Cumming (murrayc) wrote :

That is in the glom 1.3.10 upstream source tarball that I have just released. I'm not using Feisty, so I'd like someone to confirm that it works.

Revision history for this message
Murray Cumming (murrayc) wrote :

This is fixed in the latest Ubuntu upload.

Changed in glom:
status: Unconfirmed → Fix Committed
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

Package 1.3.11-0ubuntu1 built and uploaded into archives.

Changed in glom:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.