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

From Magnus Hagander
Subject Re: Make SIGHUP less painful if pg_hba.conf is not readable
Date
Msg-id 49AFCC3A.1070909@hagander.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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Joshua Tolley wrote:
> On Wed, Mar 04, 2009 at 10:28:42AM +0100, Magnus Hagander wrote:
>> Joshua Tolley wrote:
>>> On Wed, Mar 04, 2009 at 09:43:55AM +0100, Magnus Hagander wrote:
>>>> So. I've updated the comment, and applied your patch. Thanks!
>>> What would it take to get it applied to a few earlier versions as well?
>> I guess you maintaining your own fork? ;-)
>>
>>
>> Simply put, earlier versions threw away the contents of pg_hba and
>> reloaded it completely. The support for keeping the old one around in
>> case of syntax errors is new for 8.4. You'd basically require
>> backpatching of large parts of that patch, and that's not going to happen.
>>
>> //Magnus
> 
> Given that we ran into the problem in 8.3.6, how about something like
> the attached to apply to it?

Yeah, the big question is if we want to backport something like this at
all... Thoughts?

//Magnus


pgsql-hackers by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Constraint exclusion extension
Next
From: Alvaro Herrera
Date:
Subject: Re: building pg_dump doesn't work