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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, 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:59:42
Message-ID: 5901.980722782@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2001-01-28 23:00:35 Re: Re: Sure enough, the lock file is gone
Previous Message Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= 2001-01-28 22:59:08 Re: Re: Sure enough, the lock file is gone