[Tickets #13250] PostgreSQL use with Sockets not possible if custom Port is used

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/13250
------------------------------------------------------------------------------
  Ticket           | 13250
  Erstellt Von     | oldshatterhand at gmx-topmail.de
  Zusammenfassung  | PostgreSQL use with Sockets not possible if custom Port
                   | is used
  Warteschlange    | Horde Groupware Webmail Edition
  Version          | 5.1.4
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


oldshatterhand at gmx-topmail.de (2014-06-05 15:57) hat geschrieben:

If you try to run Horde with a specific PostgreSQL setup it is not possible.

Assume the following setup:

PostgreSQL is running on a custom port for TCP connections.
Horde should connect to the PostgreSQL DB using unix sockets.

Now PostgreSQL always includes the Port Number in the Socket filename.

In Horde you can, if using PgSQL, specify only the path where the  
socket file is. If you try to type the direct path to the file there  
it assumes that this file is a directory and searches for a  
subdirectory with that name and a socket file inside.

Now Horde alway searches just for a socket file with the default port.  
(".s.PGSQL.5432").
If the socket file has an other name (through a custom TCP port) this  
results in a fatal error.

I think either to give the possibility to specify the socket filepath  
instead of a directory path or adding a field for a custom port in the  
socket config-view  should resolve this problem.