Re: Make SIGHUP less painful if pg_hba.conf is not readable

From: Joshua Tolley <eggyknap(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
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-04 14:19:55
Message-ID: 20090304141954.GJ25872@eddie
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

- Josh / eggyknap

Attachment Content-Type Size
postmaster_sighup.8-3-6.patch text/x-diff 507 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua Tolley 2009-03-04 14:34:54 SYNONYMs revisited
Previous Message Heikki Linnakangas 2009-03-04 13:58:21 Re: SIGHUP during recovery