Skip site navigation (1) Skip section navigation (2)

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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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:44:10
Message-ID: 45DB417A.90202@dunslane.net (view raw or flat)
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 lets you put the file in any arbitrary location. If it's not 
set then libpq looks in the default location. See 
http://www.postgresql.org/docs/current/static/libpq-pgpass.html and 
src/interfaces/libpq/fe-connect.c

We've had this since 8.1 IIRC - I've actually found it quite useful.

cheers

andrew


In response to

pgsql-committers by date

Next:From: Bruce MomjianDate: 2007-02-20 18:47:26
Subject: pgsql: Update information_schema documentation to match system tables.
Previous:From: Tom LaneDate: 2007-02-20 18:43:47
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group