From: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pg_hba_file_settings view patch |
Date: | 2016-08-15 11:17:21 |
Message-ID: | CAJrrPGerH4jiwpcXT1-46QXUDmNp2QDrG9+-Tek_xC8APHShYw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi All,
While working on pg_hba_lookup function that can be used to lookup for an client
authentication that can be matched for given input parameters, Tom raised some
concrete use case issues in the following mail [1]. In this same
thread, he raised
some advantages of having a view similar like pg_file_settings view
for pg_hba.conf
also.
Here I attached a patch that implements the pg_hba_file_settings view
that displays
all the rows in pg_hba.conf. In case if any error exists in the
authentication rule, the
corresponding error is displayed similar like pg_file_settings.
This view can be used to verify whether there exists any problems or
not in the pg_hba.conf
before it reloads into the system. This view cannot be used to check
similar like
pg_hba_lookup function to find out which rule maps to the
corresponding input connection.
comments?
[1] - https://www.postgresql.org/message-id/28434.1468246200%40sss.pgh.pa.us
Regards,
Hari Babu
Fujitsu Australia
Attachment | Content-Type | Size |
---|---|---|
pg_hba_file_settings_1.patch | application/octet-stream | 44.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2016-08-15 11:21:49 | Re: Declarative partitioning - another take |
Previous Message | Christoph Berg | 2016-08-15 11:13:27 | Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) |