Re: Providing catalog view to pg_hba.conf file - Patch submission

From: "Prabakaran, Vaishnavi" <vaishnavip(at)fast(dot)au(dot)fujitsu(dot)com>
To: "Magnus Hagander (magnus(at)hagander(dot)net)" <magnus(at)hagander(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission
Date: 2014-03-19 03:29:16
Message-ID: 82897A1301080E4B8E461DDAA0FFCF14FD6E@SYD1216
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Friday, Mar 14, 2014 at 9:33 PM, Maganus Hagander <magnus(at)hagander(dot)net<mailto:magnus(at)hagander(dot)net> > wrote:

>>In connection to my previous proposal about "providing catalog view to pg_hba.conf file contents" , I have developed the attached patch .
>> [Current situation]
>>Currently, to view the pg_hba.conf file contents, DB admin has to access the file from database server to read the settings. In case of huge and multiple hba files, finding the appropriate hba rules which are loaded will be difficult and take some time.

>> [What this Patch does]
>>Functionality of the attached patch is that it will provide a new view "pg_hba_settings" to admin users. Public access to the view is restricted. This view will display basic information about HBA setting details of postgresql cluster. Information to be >>shown , is taken from parsed hba lines and not directly read from pg_hba.conf files. Documentation files are also updated to include details of this new view under "Chapter 47.System Catalogs". Also , a new note is added in "chapter 19.1 The >>pg_hba.conf File"
>> [Advantage]
>>Advantage of having this "pg_hba_settings" view is that the admin can check, what hba rules are loaded in runtime via database connection itself. And, thereby it will be easy and useful for admin to check all the users with their privileges in a single >>view to manage them.
>This looks like a useful feature, so make sure you register it on
Sure, I will add it to commitfest.
>I haven't looked at the actual code yet, btu I did notice one thing at a very quick lookover at the docs - it seems to be completely ignoring the key/value parameters given on a row, and >stops reporting after the auth method? That seems bad. And also, >probably host/mask should be using the inet style datatypes and not text?

Added new column "configuration_option" to pg_hba_settings view to display the key/value parameter set. Attached the updated patch.

Thanks & Regards,
Fujitsu Australia

Attachment Content-Type Size
Catalog_view_to_HBA_settings_patch_V2.patch application/octet-stream 19.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Atri Sharma 2014-03-19 04:20:33 Re: Planner hints in Postgresql
Previous Message Tom Lane 2014-03-19 03:25:08 Re: pg_archivecleanup bug