| Summary | PostgreSQL use with Sockets not possible if custom Port is used |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | oldshatterhand (at) gmx-topmail (dot) de |
| Created | 06/05/2014 (4108 days ago) |
| Due | |
| Updated | 06/11/2014 (4102 days ago) |
| Assigned | |
| Resolved | 06/11/2014 (4102 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
commit 51efe6c38694382a242fa137b91253a9f44af456
Author: Jan Schneider <jan@horde.org>
Date: Wed Jun 11 10:16:34 2014 +0200
[jan] Allow to specify port for PostgreSQL socket connections
(
Request #13250).framework/Core/lib/Horde/Config.php | 5 ++++-
framework/Core/package.xml | 4 ++--
2 files changed, 6 insertions(+), 3 deletions(-)
http://github.com/horde/horde/commit/51efe6c38694382a242fa137b91253a9f44af456
Queue ⇒ Horde Framework Packages
Type ⇒ Enhancement
State ⇒ Accepted
Priority ⇒ 1. Low
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.
State ⇒ Not A Bug
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ PostgreSQL use with Sockets not possible if custom Port is used
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
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.