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

From: Selena Deckelmann <selena(at)endpoint(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Make SIGHUP less painful if pg_hba.conf is not readable
Date: 2009-03-04 03:54:05
Message-ID: 49ADFB5D.8040304@endpoint.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Selena Deckelmann <selena(at)endpoint(dot)com> writes:
>> From the comment in hba.c, it appears that the desired behavior is to
>> have the system ignore the failure,
>
> I'm not sure how you could possibly read that comment that way.

Right. Sorry, poor choice of words. I meant "don't die on reload",
essentially.

> It might be sane to distinguish initial load from reload, but I think
> the behavior is correct as-is for initial load.

Agreed.

> Also, if we are going to do something like this, we should make sure
> it's consistent across all the config files.

Ok. I can do that. I'll check with some other people before I send
another patch, and I'll go through the rest of the config file loads
tomorrow.

-selena

--
Selena Deckelmann
End Point Corporation
selena(at)endpoint(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2009-03-04 08:27:58 Re: [HACKERS] Maintenance announcement for alderaan/barzan/minshara.postgresql.org
Previous Message Robert Treat 2009-03-04 03:43:35 Re: Hot standby, running xacts, subtransactions