Date: Fri, 27 Feb 2015 21:12:36 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Providing catalog view to pg_hba.conf file - Patch
 submission
Message-ID: <20150228021236.GY29780@tamriel.snowman.net>
References: <20150227165950.GP29780@tamriel.snowman.net>
 <CAFj8pRBo6n4gEQV8J72R0_iXiCa-kZ+j1Ecwk+LrjZRJFN4PhQ@mail.gmail.com>
 <20150227183236.GQ29780@tamriel.snowman.net>
 <CAFj8pRD0GmDAf-4M8U=JyuDRUn5n1W3HCbL2oaKDbasLKwU4zw@mail.gmail.com>
 <20150227195529.GS29780@tamriel.snowman.net>
 <12545.1425072391@sss.pgh.pa.us>
 <CAFj8pRBctY5wDOfQB+anSd-EkqJV4usJMLiiMk2GXZeeOAWMdw@mail.gmail.com>
 <20150228004101.GV29780@tamriel.snowman.net>
 <WM!599e4298425ef18c3319f7fc9bd27ed286eab71486168169a0dec5a78d39fa0ef5754c997a735d14db9260f6177f606c!@asav-3.01.com>
 <54F11BB2.9090701@agliodbs.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="SwLo357mIESq0V3a"
Content-Disposition: inline
In-Reply-To: <54F11BB2.9090701@agliodbs.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--SwLo357mIESq0V3a
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Josh Berkus (josh@agliodbs.com) wrote:
> 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.
> >=20
> > 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.
> >=20
> > 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.
>=20
> I thought the patch in question just implemented reading the file from
> disk, and nothing else?
>=20
> Speaking for my uses, I would rather have just that for 9.5 than wait
> for something more sophisticated in 9.6.

=46rom my perspective, at least, the differences we're talking about are
not enough to raise this to a 9.5-vs-9.6 issue.  I can see the use cases
for both (which is exactly why I suggested providing both).  Having one
would be better than nothing, but I foretell lots of subsequent
complaints along the lines of "everything looks right according to
pg_hba_config, but I'm getting this error!!"  Now, perhaps that's the
right approach to go for 9.5 since it'd more-or-less force our hand to
deal with it in 9.6 properly, but, personally, I'd be happier if we
moved forward with providing both because everyone agrees that it makes
sense rather than waiting to see if user complaints force our hand.

	Thanks!

		Stephen

--SwLo357mIESq0V3a
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJU8SQUAAoJEO1sijiDR2RVfKoQAL4FgRyWrVjDMhLT+3W3Zfaw
MmD+PM6VUN0L69It9HEIfYK5I81x5o2JvOFsLUaQNhmM/9FR2EvqhApblzmAcw7E
ycxUkhcSzumEhKM5q6N+GIi/PFO+sXNg1NVtljXx3rNZM7BiGtrv8kPMSPQ2i+Ue
4Yc7hVEhVsjMiPDD/9wWxj4L2ZdzgsGdVWDe3Wmx80yM+cu7RhEUe5E3NhKsg+VV
ytOR6JHktWMzJgT7SPM+m6jLBWAK4/vU6KMrHa4ObxG0lsuR72yxGxSfO7QkS42g
rHKh8CLaH4sijwqSMY0Fl1+9yZj9xXj3/Tugbsf3EkNAr559X6Abg7oW5+QG2kIp
7AvubXaB7Ha6o9VjkhWdw3rPGbfxtk/zbArjIzo8eZU8EpS8JtthSwRl8tYgyc5a
fecs8pIvh7yITf6UCiY+GEwcxTCTS7sr529W4Q/N2msVssKxQvtdW2nQRgxzZ2Qp
jdchqM3ZO6q9mdkfgbeUwb1UW8rGnhrltbgWxdUMmt2VKO6g9Gg8UwskzgDTIDGh
9IZux1ODi/lGTlgAMFuBgaFSp5rH8ud8f3bRkMADqVJTjtM9Ktk6Kdqa8s80j0O3
PLgIqIsS/64FADfHxsHijJnzp6fvd16LGd1ajJuW69/vdU6F+c+wgXbogug2Dw7M
n1xsq45mFDZy6c24mitH
=QoHU
-----END PGP SIGNATURE-----

--SwLo357mIESq0V3a--