From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
Cc: | Selena Deckelmann <selena(at)endpoint(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Make SIGHUP less painful if pg_hba.conf is not readable |
Date: | 2009-03-05 12:57:30 |
Message-ID: | 49AFCC3A.1070909@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-03-05 13:12:08 | Re: building pg_dump doesn't work |
Previous Message | Boszormenyi Zoltan | 2009-03-05 12:15:05 | Constraint exclusion extension |