Re: Q: pg_hba.conf separate database names file format

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Q: pg_hba.conf separate database names file format
Date: 2022-11-10 04:23:24
Message-ID: Y2x8vPhONZYXyYhz@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 09, 2022 at 04:02:43AM -0600, Ron wrote:
> Are these "include" files supposed to solve the problem of having a *lot* of
> databases (or users) that you want to allow access to?

Yes, splitting the list of users and database eases the maintenance
and readability of pg_hba.conf as each HBA entry could get quite
long depending on the connection policy you may want. My take would
be to use one entry per line in an @ file in this case.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Igor Korot 2022-11-10 04:40:49 List user databases
Previous Message Ajin Cherian 2022-11-10 04:04:49 Re: Support logical replication of DDLs