Re: pg_ctl -w vs unix_socket_directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 23:13:51
Message-ID: 11786.1190157231@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Radoslaw Zielinski <radek42(at)gmail(dot)com> writes:
> "pg_ctl -w -D ... start" doesn't work when unix_socket_directory is set
> to somewhere else than the compiled in default ("/tmp").

pg_ctl not working is going to be the very least of your worries;
pretty much nothing else will either.

If you want some other socket directory, I strongly recommend setting
the path to it at compile time so that it's properly wired into libpq.
AFAICS the only value in specifying unix_socket_directory at server
start is if you actually *want* a stealth server that won't be found
by clients without manual intervention.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-18 23:23:52 Re: pg_ctl -w vs unix_socket_directory
Previous Message Andrew Dunstan 2007-09-18 23:08:55 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter