Re: pg_hba_lookup function to get all matching pg_hba.conf entries - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_hba_lookup function to get all matching pg_hba.conf entries
Date
Msg-id 26519.1450885038@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_hba_lookup function to get all matching pg_hba.conf entries  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
Responses Re: pg_hba_lookup function to get all matching pg_hba.conf entries  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
"Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de> writes:
> 1. Have you considered re-loading the HBA file upon call to this function
> in a local context instead of keeping it in the backends memory?

Aside from the security questions, please consider that this feature should
work similarly to the current implementation of the pg_file_settings view,
namely it tells you about what is *currently* in the on-disk files, not
necessarily what is the active setting in the postmaster's memory.
A backend could not be entirely sure about the postmaster's state anyway;
and even if it could be, one of the major applications for features like
this is testing manual changes to the files before you SIGHUP the
postmaster.  So re-reading the files on each usage is a Good Thing, IMO,
even if it sounds inefficient.

> 2. I also wonder why JSONB arrays for database/user instead of TEXT[]?

Yes, that seems rather random to me too.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Dmitry Ivanov
Date:
Subject: Re: [PROPOSAL] Backup and recovery of pg_statistic
Next
From: Fabien COELHO
Date:
Subject: Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule?