Received: from mta01.mail.mel.aone.net.au (mta01.mail.au.uu.net [203.2.192.81]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f692p4a69546 for ; Sun, 8 Jul 2001 22:51:04 -0400 (EDT) (envelope-from justin@postgresql.org) Received: from postgresql.org ([63.34.218.104]) by mta01.mail.mel.aone.net.au with ESMTP id <20010709025058.JZHD18810.mta01.mail.mel.aone.net.au@postgresql.org>; Mon, 9 Jul 2001 12:50:58 +1000 Message-ID: <3B491AA4.F7C51A7D@postgresql.org> Date: Mon, 09 Jul 2001 12:44:52 +1000 From: Justin Clift X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Kings-Lynne CC: Tom Lane , Peter Eisentraut , Bruce Momjian , "Damien =?iso-8859-1?Q?Clermont=E9?=" , pgsql-patches@postgresql.org Subject: Re: [PATCH] Patch to make pg_hba.conf handle virtualhost access control and samehost keyword References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200107/31 X-Sequence-Number: 1228 How about moving the documentation to a pg_hba.conf.README file? People shouldn't be able to miss that very easily. + Justin Christopher Kings-Lynne wrote: > > > > Maybe it should be cached in memory and only be re-read on request > > > (SIGHUP). Parsing that file every time is undoubtedly a large > > fraction of > > > the total connection startup time. > > > > Okay with me if someone wants to do it ... but that'd be a lot more work > > than just moving the documentation ... > > Or cache the information and just do a file modification timestamp check on > each connection to see if it needs to be reread. (Best of both worlds??) > > Chris > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://www.postgresql.org/search.mpl