Re: pg_ctl -w vs unix_socket_directory

From: Radoslaw Zielinski <radek42(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_ctl -w vs unix_socket_directory
Date: 2007-09-18 23:00:14
Message-ID: 20070918230014.GA14511@bzium
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. :-)

--
Radosław Zieliński <radek(at)pld-linux(dot)org>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-09-18 23:02:53 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous Message Andrew Dunstan 2007-09-18 22:42:14 Re: pg_ctl -w vs unix_socket_directory