On 19/09/2007, Tom Lane [EMAIL PROTECTED] wrote:
Radoslaw Zielinski [EMAIL PROTECTED] 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
On Tue, 2007-09-18 at 19:13 -0400, Tom Lane wrote:
Radoslaw Zielinski [EMAIL PROTECTED] 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;
Hello,
pg_ctl -w -D ... start doesn't work when unix_socket_directory is set
to somewhere else than the compiled in default (/tmp). Having this is
useful for the startup scripts, so the status DONE actually means
success, instead of maybe.
Jeff Davis wrote about it a while ago:
This has a trivial workaround - just set PGHOST for pg_ctl:
[EMAIL PROTECTED] inst.codfix.5705]$
PGHOST=/home/andrew/pgl/inst.codfix.5705 bin/pg_ctl -D data/ -l logfile
-w start
waiting for server to start done
server started
[EMAIL PROTECTED] inst.codfix.5705]$
cheers
andrew
Andrew Dunstan [EMAIL PROTECTED] [18-09-2007 23:42]:
This has a trivial workaround - just set PGHOST for pg_ctl:
[EMAIL PROTECTED] inst.codfix.5705]$
PGHOST=/home/andrew/pgl/inst.codfix.5705 bin/pg_ctl -D data/ -l logfile -w
start
That would be fine for a particular installation, but isn't
Radoslaw Zielinski [EMAIL PROTECTED] 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
Radoslaw Zielinski wrote:
Andrew Dunstan [EMAIL PROTECTED] [18-09-2007 23:42]:
This has a trivial workaround - just set PGHOST for pg_ctl:
[EMAIL PROTECTED] inst.codfix.5705]$
PGHOST=/home/andrew/pgl/inst.codfix.5705 bin/pg_ctl -D data/ -l logfile -w
start
That would be
