| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "Trond Eivind =?iso-8859-1?Q?Glomsr=F8d?=" <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:13:30 |
| Message-ID: | 3A74A79A.AC68839E@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> > How about an environment variable? PGSOCKLOC? Use the hard-coded
> > default if the envvar not set? This way multiple postmasters running on
> > multiple sockets can be smoothly supported.
> It's spelled PGHOST as of 7.1 ... but the discussion here is about what
> the default behavior of an installation will be, not what you can
> override it to do.
I'm talking about Unix domain socket location, not TCP/IP hostname,
which PGHOST is, right?
But you are very right -- this doesn't help the default. The
FHS-mandated place for such a configuration file detailing such settings
is in /etc -- but, of course, we support installations that have been
installed by a non-root user. ISTM a 'pg_config --default-socket'
command could be used to find the location, assuming pg_config is on the
PATH.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2001-01-28 23:19:15 | Re: Re: Sure enough, the lock file is gone |
| Previous Message | Tom Lane | 2001-01-28 23:06:39 | Re: Re: Sure enough, the lock file is gone |