| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Adjust user-facing documentation to explain why we don't check |
| Date: | 2007-02-20 18:34:04 |
| Message-ID: | 200702201834.l1KIY4B15046@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Andrew Dunstan wrote:
> Tom Lane wrote:
> > Log Message:
> > -----------
> > Adjust user-facing documentation to explain why we don't check pgpass
> > file permissions on Windows.
> >
>
> +On Microsoft Windows, the file is stored in a directory that is secure by
> +default, so no special permissions check is made.
>
>
>
> I doubt this is true if PGPASSFILE is set.
I thought it would be in the user's Application Data directory, or are
you saying they might put it somewhere else?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-02-20 18:39:23 | Re: pgsql: Adjust user-facing documentation to explain why we don't check |
| Previous Message | Andrew Dunstan | 2007-02-20 18:23:47 | Re: pgsql: Adjust user-facing documentation to explain why we don't check |