reassign 313507 libpq4 severity 313507 important thanks On Tue, Jun 14, 2005 at 06:59:12AM +0200, Pierre Pronchery wrote: > Package: php4-pgsql > Version: 3:4.3.10-5 > Severity: grave > Justification: renders package unusable
> it seems that after my upgrade to postgresql-7.4, php can't connect > anymore to the SQL server locally. It looks for the UNIX socket in > /tmp/.s.PGSQL.5432 while it is actually in > /var/run/postgresql/.s.PGSQL.5432. > I don't remember having changed anything about the location of the > socket, either in PHP or Postgres configuration files. Although, it is > possible to workaround this, for instance: > # ln -sf /var/run/postgresql/.s.PGSQL.5432 /tmp/.s.PGSQL.5432 > I just thought this would certainly harm only local connections, so I > set the severity to "Grave" in the first place, but feel free to lower > it if you think it won't affect a vast majority of users. Another > workaround then could be to allow local TCP connections and use the > loopback address (which is the default iirc). This cannot be a bug in php4-pgsql; php4-pgsql doesn't pick the location of the socket being used, this is a default that comes from the postgresql lib. For that matter, php4-pgsql supports specifying an alternative path to the Unix socket, using the host and port options, so this bug shouldn't be grave. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
