Postgres Pro
Downloads
Home   >   mailing lists

Re: Make SIGHUP less painful if pg_hba.conf is not readable - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Make SIGHUP less painful if pg_hba.conf is not readable
Date
Msg-id 200903052116.20642.peter_e@gmx.net
Whole thread Raw
In response to Re: Make SIGHUP less painful if pg_hba.conf is not readable  (Joshua Tolley <eggyknap@gmail.com>)
Responses Re: Make SIGHUP less painful if pg_hba.conf is not readable  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Tree view 
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 by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Expanding the length of a VARCHAR column should not induce a table rewrite
Next
From: Magnus Hagander
Date:
Subject: Re: Make SIGHUP less painful if pg_hba.conf is not readable