pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Q: pg_hba.conf separate database names file format
Date: Wed, 9 Nov 2022 04:02:43 -0600
Message-ID: <14a96ca8-cba4-ec09-4420-b71c0719e8c8@gmail.com> (raw)
In-Reply-To: <Y2s4XhNV6AFQiMSm@paquier.xyz>
References: <NXFJVAUX.C35JFJNY.4IYT4D2Y@I56PTRRI.6PUFY6O7.54SL26VD>
	<Y2s4XhNV6AFQiMSm@paquier.xyz>

On 11/8/22 23:19, Michael Paquier wrote:
> On Tue, Nov 08, 2022 at 02:16:03PM +0100, Albrecht Dreß wrote:
>> However, I could not find a specification of the format for this
>> file…  It appears as if simply giving each database name on a
>> separate line does the job.  Is this correct?  May the file contain
>> comments (i.e. lines starting with “#”) or empty lines?  May the
>> file be specified including a path (e.g. “@/some/path/databases”)?
> I have been playing with this code for the last couple of days, and
> the answer is that you can use an absolute path or a relative path.
> In the case of a relative path, the code considers the base directory
> as the parent directory of the file this is included in.  For example,
> /data/pg/pg_hba.conf including a @databases.conf resolves as
> /data/pg/databases.conf, and a @conf/databases.conf resolves as
> /data/pg/conf/databases.conf.
>
> The parsing of these files uses the same rules as what's done for
> pg_hba.conf and pg_ident.conf, so you can specify a list of
> user names separated by commas or even spaces, or put one name per
> line.  Comments beginning with '#' are ignored.
>
> If you want to play with your file and see the results, I would
> recommend to tweak the files, and then look at the contents generated
> in the system view pg_hba_file_rules.  Querying pg_hba_file_rules
> loads directly the configuration files from disk, so there is no need
> to reload or restart the server to see the effects any modifications
> would have.
>
> The documentation has already some descriptions, that you've missed,
> perhaps:
> https://www.postgresql.org/docs/15/auth-pg-hba-conf.html
> "Files included by @ constructs are read as lists of names, which can
> be separated by either whitespace or commas. Comments are introduced
> by #, just as in pg_hba.conf, and nested @ constructs are
> allowed. Unless the file name following @ is an absolute path, it is
> taken to be relative to the directory containing the referencing
> file."

Are these "include" files supposed to solve the problem of having a *lot* of 
databases (or users) that you want to allow access to?

-- 
Angular momentum makes the world go 'round.

view thread (4+ messages)  latest in thread

Message-ID: <14a96ca8-cba4-ec09-4420-b71c0719e8c8@gmail.com>
Permalink:  ../14a96ca8-cba4-ec09-4420-b71c0719e8c8@gmail.com/
Also on:    postgresql.org/message-id/14a96ca8-cba4-ec09-4420-b71c0719e8c8@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: Q: pg_hba.conf separate database names file format
  In-Reply-To: <14a96ca8-cba4-ec09-4420-b71c0719e8c8@gmail.com>
  References: <NXFJVAUX.C35JFJNY.4IYT4D2Y@I56PTRRI.6PUFY6O7.54SL26VD> <Y2s4XhNV6AFQiMSm@paquier.xyz> <14a96ca8-cba4-ec09-4420-b71c0719e8c8@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox