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 49AE49CA.3070606@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  (Joshua Tolley <eggyknap@gmail.com>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Immediate shutdown and system(3)
Next
From: Guillaume Smet
Date:
Subject: Re: [BUGS] BUG #4689: Expanding the length of a VARCHAR column should not induce a table rewrite