Re: use has_privs_of_role() for pg_hba.conf

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Joshua Brindle <joshua(dot)brindle(at)crunchydata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: use has_privs_of_role() for pg_hba.conf
Date: 2022-10-11 05:01:07
Message-ID: Y0T4kwYUobg09gPX@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 09, 2022 at 02:13:48PM -0700, Nathan Bossart wrote:
> Here you go.

Thanks, applied. It took me a few minutes to note that
regress_regression_* is required in the object names because we need
to use the same name for the parent role and the database, with
"regress_" being required for the role and "regression" being required
for the database. I have added an extra section where pg_hba.conf is
set to match only the parent role, while on it. perltidy has reshaped
things in an interesting way, because the generated log_[un]like is
long, it seems.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2022-10-11 05:31:23 Re: PostgreSQL Logical decoding
Previous Message Bharath Rupireddy 2022-10-11 04:04:25 Re: Suppressing useless wakeups in walreceiver