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

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: pgsql: Adjust user-facing documentation to explain why we don't check
Дата
Msg-id 45DB415F.9000702@hagander.net
обсуждение исходный текст
Ответ на Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Dave Page <dpage@postgresql.org>)
Список pgsql-committers
>> PGPASSFILE takes a full path name, so you can put the file anywhere you
>> want. Just like on Unix.
>
> OK, so we _do_ need to check the permissions on pgpass on Win32, but we
> just don't know how to do that?
>

If we _need_ to check, I don't know. If you've set PGPASSFILE to
something, then you've made a decision to change from the default, and
it could be argued that we don't have to check for that. It can of
course equally well be argued that we should, yes.

Which would bring is to the "how". If there was an easy way to do the
how, we should probably do it. However, I'm very concerned that we will
break a whole lot more than we fix because the permissions system is
much more complex.

//Magnus

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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: 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