Re: Re: Sure enough, the lock file is gone

Поиск
Список
Период
Сортировка
От Lamar Owen
Тема Re: Re: Sure enough, the lock file is gone
Дата
Msg-id 3A74A79A.AC68839E@wgcr.org
обсуждение исходный текст
Ответ на Re: Re: Sure enough, the lock file is gone  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: Re: Sure enough, the lock file is gone  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane wrote:
> Lamar Owen <lamar.owen@wgcr.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Re: Sure enough, the lock file is gone
Следующее
От: Lamar Owen
Дата:
Сообщение: Re: Re: Sure enough, the lock file is gone