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

From Joshua Tolley
Subject Re: Make SIGHUP less painful if pg_hba.conf is not readable
Date
Msg-id 20090305214342.GR25872@eddie
Whole thread Raw
In response to Re: Make SIGHUP less painful if pg_hba.conf is not readable  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Thu, Mar 05, 2009 at 08:19:05PM +0100, Magnus Hagander wrote:
> Peter Eisentraut wrote:
> > 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).
>
> That's what we do in the proper fix in HEAD. It requires an API change
> to backport it...
>
> Given that I think this is the first time we've heard of this issue, I'm
>  thinking we should probably just not bother to backpatch it.

I'm inclined to agree, FWIW.

- Josh / eggyknap

pgsql-hackers by date:

Previous
From: Xuân Baldauf
Date:
Subject: Re: Re: [BUGS] BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite
Next
From: Tom Lane
Date:
Subject: Re: GIN, partial matches, lossy bitmaps