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

From Bruce Momjian
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id 200101282354.SAA15528@candle.pha.pa.us
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Peter Eisentraut <peter_e@gmx.net> writes:
> > Perhaps there could be some sort of /etc/postgresql.conf file that is read
> > by both client and server that can control these sort of aspects.
> 
> Maybe ... but it seems to me that still leaves us with the issue of
> a single pathname that must be known a-priori to both client and server.
> You've just changed that path from "/tmp/..." to "/etc/...".

And writing to /etc requires root permissions.  That is the restriction
that got us into /tmp in the first place.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: teg@redhat.com (Trond Eivind Glomsrød)
Date:
Subject: Re: Re: Sure enough, the lock file is gone
Next
From: Tom Lane
Date:
Subject: Re: Re: Sure enough, the lock file is gone