From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Trond Eivind Glomsrød <teg(at)redhat(dot)com>, The Hermit Hacker <scrappy(at)hub(dot)org>, Florent Guillaume <efgeor(at)noos(dot)fr>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: Sure enough, the lock file is gone |
Date: | 2001-01-28 23:54:18 |
Message-ID: | 200101282354.SAA15528@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Peter Eisentraut <peter_e(at)gmx(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-29 01:00:32 | Re: Re: Sure enough, the lock file is gone |
Previous Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-01-28 23:43:51 | Re: Re: Sure enough, the lock file is gone |