| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Arcady Genkin <a(dot)genkin(at)utoronto(dot)ca> |
| Cc: | Postgres-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: REPOST: redefining location of the socket file /tmp/.s.PGSQL.5432 |
| Date: | 2001-06-12 20:17:42 |
| Message-ID: | 13519.992377062@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Arcady Genkin <a(dot)genkin(at)utoronto(dot)ca> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Can I redefine location of the UNIX domain socket file to be other
> than /tmp/.s.PGSQL.5432?
>>
>> Yes, in 7.1 this is a supported option. See unix_socket_directory
>> parameter.
> Thanks a lot, this is what I was looking for. I have another
> question, though: how are the clients (mod_php4 for e.g.) going to
> know the non-standard location of the socket file?
They're not, unless you tell them, which is why runtime setting of the
parameter isn't all that useful IMHO. But some people wanted it, so
there it is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arcady Genkin | 2001-06-12 20:42:31 | PHP's pg_connect() and non-standard location of the socket (was: REPOST: redefining location of the socket file /tmp/.s.PGSQL.5432) |
| Previous Message | Arcady Genkin | 2001-06-12 20:13:17 | Re: REPOST: redefining location of the socket file /tmp/.s.PGSQL.5432 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-12 20:20:12 | Re: Re: very big problem with NULL |
| Previous Message | Arcady Genkin | 2001-06-12 20:13:17 | Re: REPOST: redefining location of the socket file /tmp/.s.PGSQL.5432 |