Re: pgsql: Adjust user-facing documentation to explain why we don't check - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql: Adjust user-facing documentation to explain why we don't check
Date
Msg-id 200702201834.l1KIY4B15046@momjian.us
Whole thread Raw
In response to Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pgsql: Adjust user-facing documentation to explain why we don't check
Re: pgsql: Adjust user-facing documentation to explain why we don't check
List 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@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

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

pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Next
From: Magnus Hagander
Date:
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check