Re: pg_ctl -w vs unix_socket_directory

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_ctl -w vs unix_socket_directory
Date: 2007-09-18 23:23:52
Message-ID: 46F05E08.5080701@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Radoslaw Zielinski wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> [18-09-2007 23:42]:
>
>> This has a trivial workaround - just set PGHOST for pg_ctl:
>>
>
>
>> [andrew(at)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-09-18 23:25:36 Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous Message Tom Lane 2007-09-18 23:13:51 Re: pg_ctl -w vs unix_socket_directory