On 22.02.2010 23:38, Bruce Momjian wrote:
Michael Renner wrote:
>
Looking through the available variables probably only PGHOST seems to be
of interest for pg_ctl's purposes; psql's manpage already refers to The
Documentation for further variables and information. What's needed in
pg_ctl's case
Michael Renner wrote:
> Alvaro Herrera wrote:
> > Michael Renner wrote:
> >
> >> Mentioning PGHOST in pg_ctl's
> >> manpage/documentation should make this entirely clear for people who
> >> aren't familiar with the extensive environment variables PostgreSQLs
> >> client library can use. [1]
> >
>
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> My current feeling about it is that setting unix_socket_directory as a
> >> configuration parameter is only useful to those who are deliberately
> >> trying to hide their postmaster from regular clients, in which case
> >> the fact t
Bruce Momjian writes:
> Tom Lane wrote:
>> My current feeling about it is that setting unix_socket_directory as a
>> configuration parameter is only useful to those who are deliberately
>> trying to hide their postmaster from regular clients, in which case
>> the fact that pg_ctl -w fails could be
Tom Lane wrote:
> My current feeling about it is that setting unix_socket_directory as a
> configuration parameter is only useful to those who are deliberately
> trying to hide their postmaster from regular clients, in which case
> the fact that pg_ctl -w fails could be seen as a feature not a bug.
Alvaro Herrera wrote:
Michael Renner wrote:
Mentioning PGHOST in pg_ctl's
manpage/documentation should make this entirely clear for people who
aren't familiar with the extensive environment variables PostgreSQLs
client library can use. [1]
Yeah, this has been complained about many, many times
Michael Renner wrote:
> Mentioning PGHOST in pg_ctl's
> manpage/documentation should make this entirely clear for people who
> aren't familiar with the extensive environment variables PostgreSQLs
> client library can use. [1]
Yeah, this has been complained about many, many times.
> If this is a
Tom Lane wrote:
My current feeling about it is that setting unix_socket_directory as a
configuration parameter is only useful to those who are deliberately
trying to hide their postmaster from regular clients, in which case
the fact that pg_ctl -w fails could be seen as a feature not a bug.
The
Alvaro Herrera writes:
> Michael Renner wrote:
>> When using a non-standard unix_socket_directory setting, pg_ctl -w (re)start
>> fails because it checks for the socket file to appear in it's default
>> location.
> Yeah, this has been discussed before. It's been suggested that pg_ctl
> should pa
Michael Renner wrote:
> When using a non-standard unix_socket_directory setting, pg_ctl -w (re)start
> fails because it checks for the socket file to appear in it's default
> location.
Yeah, this has been discussed before. It's been suggested that pg_ctl
should parse postgresql.conf to figure ou
The following bug has been logged online:
Bug reference: 5103
Logged by: Michael Renner
Email address: michael.ren...@amd.co.at
PostgreSQL version: HEAD
Operating system: Linux
Description:"pg_ctl -w (re)start" fails with custom
unix_socket_directory
Details:
When u
11 matches
Mail list logo
