Re: Make SIGHUP less painful if pg_hba.conf is not readable

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Make SIGHUP less painful if pg_hba.conf is not readable
Дата
Msg-id 200903052116.20642.peter_e@gmx.net
обсуждение исходный текст
Ответ на Re: Make SIGHUP less painful if pg_hba.conf is not readable  (Joshua Tolley <eggyknap@gmail.com>)
Ответы Re: Make SIGHUP less painful if pg_hba.conf is not readable
Список pgsql-hackers
Дерево обсуждения 
On Thursday 05 March 2009 18:04:42 Joshua Tolley wrote:
> As an aside, is access() adequately portable, ok to use within the
> backend, etc.? I just sort of took a shot in the dark.

Using access() is usually not a good idea.  In this case it would be better to 
check the return of the actual open() call for EPERM (or the equivalent for 
fopen(), whatever is used).

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

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Expanding the length of a VARCHAR column should not induce a table rewrite
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: Make SIGHUP less painful if pg_hba.conf is not readable