On 08/20/11 8:31 AM, Robert Hopek wrote:
The following bug has been logged online:
Bug reference: 6171
Logged by: Robert Hopek
Email address: rho...@getnetworks.com
PostgreSQL version: 8.1.23
Operating system: CentOS/RHEL
Description: Sockets Issue
Details:
Why do you have the configuration option to change the pgsql socket (which
we need to do for our jailed shell environment), but not have psql check the
postgresql.conf file for the enablement of that location change so that psql
would look there automatically? It seems very counter-productive. While
psql, as well as functions in languages like PHP (pg_connect) allow for an
override so that you could point it at the new location (when custom
coding), existing software, such as phpPgAdmin, are stuck only looking in
/tmp for it. We consider it a bug that the server supports a configuration
option the clients do not inherently support by checking the configuration
of the server.
libpq running in the client user's context usually has no access to the
postgresql.conf file which is generally in a mode 700 directory owned by
the service account.
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
