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

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: pgsql: Adjust user-facing documentation to explain why we don't check
Дата
Msg-id 45DB417A.90202@dunslane.net
обсуждение исходный текст
Ответ на Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Bruce Momjian <bruce@momjian.us>)
Список 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


В списке pgsql-committers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Adjust user-facing documentation to explain why we don't check