Re: Providing catalog view to pg_hba.conf file - Patch submission - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Providing catalog view to pg_hba.conf file - Patch submission
Date
Msg-id 54F11BB2.9090701@agliodbs.com
Whole thread Raw
In response to Re: Providing catalog view to pg_hba.conf file - Patch submission  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: Providing catalog view to pg_hba.conf file - Patch submission  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 02/27/2015 04:41 PM, Stephen Frost wrote:
>> we can do copy of pg_hba.conf somewhere when postmaster starts or when it
>> is reloaded.
> 
> Please see my reply to Tom.  There's no trivial way to reach into the
> postmaster from a backend- but we do get a copy of whatever the
> postmaster had when we forked, and the postmaster only reloads
> pg_hba.conf on a sighup and that sighup is passed down to the children,
> so we simply need to also reload the pg_hba.conf in the children when
> they get a sighup.
> 
> That's how postgresql.conf is handled, which is what pg_settings is
> based off of, and I believe is the behavior folks are really looking
> for.

I thought the patch in question just implemented reading the file from
disk, and nothing else?

Speaking for my uses, I would rather have just that for 9.5 than wait
for something more sophisticated in 9.6.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: [COMMITTERS] pgsql: Invent a memory context reset/delete callback mechanism.
Next
From: Tom Lane
Date:
Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission