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

From Andrew Dunstan
Subject Re: pg_ctl -w vs unix_socket_directory
Date
Msg-id 46F05446.5030203@dunslane.net
Whole thread Raw
In response to pg_ctl -w vs unix_socket_directory  (Radoslaw Zielinski <radek42@gmail.com>)
Responses Re: pg_ctl -w vs unix_socket_directory
List pgsql-hackers
This has a trivial workaround - just set PGHOST for pg_ctl:

[andrew@constanza 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
[andrew@constanza inst.codfix.5705]$

cheers

andrew


Radoslaw Zielinski wrote:
> 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:
> http://svr5.postgresql.org/pgsql-general/2006-09/msg01141.php
>
>
> Simple hacky patch for v8.2.5; maybe someone finds it useful before
> the proper config parser is integrated:
> http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/postgresql-pg_ctl-fix.patch?rev=HEAD
>
>   


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter