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 46F05E08.5080701@dunslane.net
Whole thread Raw
In response to Re: pg_ctl -w vs unix_socket_directory  (Radoslaw Zielinski <radek42@gmail.com>)
List pgsql-hackers

Radoslaw Zielinski wrote:
> Andrew Dunstan <andrew@dunslane.net> [18-09-2007 23:42]:
>   
>> 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
>>     
>
> That would be fine for a particular installation, but isn't really
> suitable for a startup script shipped with a linux distribution.  Sure,
> a /bin/sh-based postgresql.conf parser could do the trick... but I just
> don't feel like writing one. :-)
>
>   

I think it's broken for a distro to ship with config files setting a 
socket dir other than the one they compile in.

If you don't like /tmp compile in something else. The you don't need to 
parse anything.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_ctl -w vs unix_socket_directory
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter