Re: pg_ctl -w vs unix_socket_directory

On 19/09/2007, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Radoslaw Zielinski <radek42(at)gmail(dot)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.