[Tickets #13250] Re: 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
  Aktualisiert 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           | Not A Bug
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


oldshatterhand at gmx-topmail.de (2014-06-10 20:52) hat geschrieben:

> This is a limitation of how PHP's PDO API connects.

Thanks for your Reply.
While waiting for it I found a solution for the Problem.

I inserted
"$conf['sql']['port'] = portnumber;"

manually into the conf.php atfer

"$conf['sql']['socket'] = 'socketpath';"

Now it works without any problems and horde uses the socket as it should.

So I'd like to change this bug report into a feature request:

Addming a "Port" Field, that fills the "$conf['sql']['port'] " in  
config.php, to the Config UI for PgSQL (with Socket) would make the  
configuration much more comfortable and easy to understand for users  
that also have the I had.