Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Add documentation for Windows on how to set an environment

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Add documentation for Windows on how to set an environment
Date: 2007-02-05 22:41:39
Message-ID: 200702052241.l15Mfdx09774@momjian.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > Bruce Momjian wrote:
> >> I think environment variables are used rarely enough on Win32 that we
> >> should supply a hint.
> 
> > I think every Windows administrator who is not totally clueless knows 
> > how to set the environment. Maybe home users don't use it much, but 
> > admins certainly need to know about it.
> 
> Another argument against it is that the libpq documentation is an
> entirely random place to discuss it, as libpq is hardly the only part of
> Postgres that responds to environment variables.
> 
> I liked the idea of mentioning it in the Windows FAQ, instead.

OK, sure.  Magnus.

-- 
  Bruce Momjian   bruce(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

Next:From: Stephan SzaboDate: 2007-02-05 23:07:16
Subject: Re: Referential Integrity and SHARE locks
Previous:From: Tom LaneDate: 2007-02-05 22:39:23
Subject: Re: Re: [COMMITTERS] pgsql: Add documentation for Windows on how to set an environment

pgsql-committers by date

Next:From: James William PyeDate: 2007-02-05 23:35:03
Subject: python - tin: Specify more impatient modes when stopping a cluster.
Previous:From: Tom LaneDate: 2007-02-05 22:39:23
Subject: Re: Re: [COMMITTERS] pgsql: Add documentation for Windows on how to set an environment

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group