diff options
| author | Michael Paquier <michael@paquier.xyz> | 2022-03-29 09:06:51 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2022-03-29 09:06:51 +0900 |
| commit | 091a971bb59ca9751f32a4aa5aee969c5a915754 (patch) | |
| tree | 6f0765d5f626d6fb129f979b4c7b9d63aa63255e /src/backend/parser/parse_expr.c | |
| parent | 33a377608fc29cdd1f6b63be561eab0aee5c81f0 (diff) | |
| download | postgresql-091a971bb59ca9751f32a4aa5aee969c5a915754.tar.gz postgresql-091a971bb59ca9751f32a4aa5aee969c5a915754.zip | |
Modify query on pg_hba_file_rules to check for errors in regression tests
The regression tests include a query to check the execution path of
pg_hba_file_rules, but it has never checked that a given cluster has
correct contents in pg_hba.conf. This commit extends the query of
pg_hba_file_rules to report any errors if anything bad is found. For
EXEC_BACKEND builds, any connection attempt would fail when loading
pg_hba.conf if any incorrect content is found when parsed, so a failure
would be detected before even running this query. However, this can
become handy for clusters where pg_hba.conf can be reloaded, where new
connection attempts are not subject to a fresh loading of pg_hba.conf.
Author: Julien Rouhaud, based on an idea from me
Discussion: https://postgr.es/m/YkFhpydhyeNNo3Xl@paquier.xyz
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions