Re: pg_ctl -w vs unix_socket_directory

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Radoslaw Zielinski <radek42(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_ctl -w vs unix_socket_directory
Date: 2007-09-18 22:42:14
Message-ID: 46F05446.5030203@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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
waiting for server to start.... done
server started
[andrew(at)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
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Radoslaw Zielinski 2007-09-18 23:00:14 Re: pg_ctl -w vs unix_socket_directory
Previous Message Andrew Dunstan 2007-09-18 22:32:33 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter