Re: [EXTERNAL] Re: [PATCH] Support using "all" for the db user in pg_ident.conf - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [EXTERNAL] Re: [PATCH] Support using "all" for the db user in pg_ident.conf
Date
Msg-id Y76YEHolPL4LIAtO@paquier.xyz
Whole thread Raw
In response to Re: [EXTERNAL] Re: [PATCH] Support using "all" for the db user in pg_ident.conf  (Jelte Fennema <Jelte.Fennema@microsoft.com>)
Responses Re: [EXTERNAL] Re: [PATCH] Support using "all" for the db user in pg_ident.conf
List pgsql-hackers
On Wed, Jan 11, 2023 at 09:04:56AM +0000, Jelte Fennema wrote:
> It's very different. I think easiest is to explain by example:
>
> If there exist three users on the postgres server: admin, jelte and michael
>
> Then this rule (your suggested rule):
> mapname /^(.*)$ \1
>
> Is equivalent to:
> mapname admin admin
> mapname jelte jelte
> mapname michael michael
>
> While with the "all" keyword you can create a rule like this:
> mapname admin all
>
> which is equivalent to:
> mapname admin admin
> mapname admin jelte
> mapname admin michael

Thanks for the explanation, I was missing your point.  Hmm.  On top
of my mind, couldn't we also use a regexp for the pg-role rather than
just a hardcoded keyword here then, so as it would be possible to
allow a mapping to pass for a group of role names?  "all" is just a
pattern to allow everything, at the end.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: meson oddities
Next
From: vignesh C
Date:
Subject: Re: Time delayed LR (WAS Re: logical replication restrictions)