pg_ctl -w vs unix_socket_directory

From: Radoslaw Zielinski <radek42(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: pg_ctl -w vs unix_socket_directory
Date: 2007-09-18 22:24:54
Message-ID: 20070918222454.GA14278@bzium
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-18 22:32:33 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous Message Tom Lane 2007-09-18 22:18:34 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter