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

From Magnus Hagander
Subject Re: pgsql: Adjust user-facing documentation to explain why we don't check
Date
Msg-id 45DB405B.9060101@hagander.net
Whole thread Raw
In response to Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pgsql: Adjust user-facing documentation to explain why we don't check
List pgsql-committers
Bruce Momjian wrote:
> 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?
>

PGPASSFILE takes a full path name, so you can put the file anywhere you
want. Just like on Unix.

//Magnus


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Next
From: Bruce Momjian
Date:
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check