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

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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:39:23
Message-ID: 45DB405B.9060101@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2007-02-20 18:40:30 Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous Message Bruce Momjian 2007-02-20 18:34:04 Re: pgsql: Adjust user-facing documentation to explain why we don't check