Re: Re: Sure enough, the lock file is gone - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id 15381.980743391@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Re: Sure enough, the lock file is gone  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: Sure enough, the lock file is gone
Next
From: Bruce Momjian
Date:
Subject: Re: Re: Sure enough, the lock file is gone