BUG #6171: Sockets Issue

Поиск
Список
Период
Сортировка
От Robert Hopek
Тема BUG #6171: Sockets Issue
Дата
Msg-id 201108201531.p7KFVFaw062983@wwwmaster.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #6171: Sockets Issue  (John R Pierce <pierce@hogranch.com>)
Re: BUG #6171: Sockets Issue  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Re: BUG #6171: Sockets Issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #6171: Sockets Issue  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-bugs
The following bug has been logged online:

Bug reference:      6171
Logged by:          Robert Hopek
Email address:      rhopek@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.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: BUG #6170: hot standby wedging on full-WAL disk
Следующее
От: Alejandro Sánchez
Дата:
Сообщение: Re: BUG #6120: Problem running post-install step in Mac OS X Lion (GM)