| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | 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 22:57:54 |
| Message-ID: | 5874.980722674@sss.pgh.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/...".
Moreover, such a setup would make it substantially more painful to run
multiple versions of Postgres on a single machine. Right now, as long
as each version has a different default port number, it works great.
Try to put the default port number in /etc/postgresql.conf, and you've
got a problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-01-28 22:59:08 | Re: Re: Sure enough, the lock file is gone |
| Previous Message | Tom Lane | 2001-01-28 22:53:10 | Re: Re: Sure enough, the lock file is gone |