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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-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. +
From | Date | Subject | |
---|---|---|---|
Next Message | James William Pye | 2007-02-05 23:35:03 | python - tin: Specify more impatient modes when stopping a cluster. |
Previous Message | Tom Lane | 2007-02-05 22:39:23 | Re: Re: [COMMITTERS] pgsql: Add documentation for Windows on how to set an environment |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2007-02-05 23:07:16 | Re: Referential Integrity and SHARE locks |
Previous Message | Tom Lane | 2007-02-05 22:39:23 | Re: Re: [COMMITTERS] pgsql: Add documentation for Windows on how to set an environment |