Re: Re: Sure enough, the lock file is gone

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, The Hermit Hacker <scrappy(at)hub(dot)org>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Sure enough, the lock file is gone
Date: 2001-01-29 04:43:11
Message-ID: 15381.980743391@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> The bottom line: yes, /tmp was a poor choice of place to put the
>> socket files. But no, it is not so poor as to be worth creating a

> Was it really a poor choice. Where else can we put it as non-root?

I would've favored something like /tmp/.postgres/socketfile,
which is comparable to typical X11 setups. But it's moot, since
we can't change the default path even that much without creating a
compatibility headache ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-01-29 04:43:55 Re: Re: Sure enough, the lock file is gone
Previous Message Bruce Momjian 2001-01-29 04:39:56 Re: Re: Sure enough, the lock file is gone