Re: pg_ctl -w vs unix_socket_directory - Mailing list pgsql-hackers

From Radosław Zieliński
Subject Re: pg_ctl -w vs unix_socket_directory
Date
Msg-id a8dae1ea0709190307r7fa72140t69d9001ce77f8079@mail.gmail.com
Whole thread Raw
In response to Re: pg_ctl -w vs unix_socket_directory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 19/09/2007, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Radoslaw Zielinski <radek42@gmail.com> writes:
> > "pg_ctl -w -D ... start" doesn't work when unix_socket_directory is set
> > to somewhere else than the compiled in default ("/tmp").
> pg_ctl not working is going to be the very least of your worries;
> pretty much nothing else will either.

> If you want some other socket directory, I strongly recommend setting
[...]

I don't want any other socket directory.  All I want is a way to
create a working startup script: able to start/stop the server
regardless of changes in postgresql.conf and report the success or
failure.


pgsql-hackers by date:

Previous
From: "Radosław Zieliński"
Date:
Subject: Re: pg_ctl -w vs unix_socket_directory
Next
From: Gregory Stark
Date:
Subject: Re: Open issues for HOT patch