Re: allow specifying direct role membership in pg_hba.conf - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: allow specifying direct role membership in pg_hba.conf
Date
Msg-id 60A31604.2050206@anastigmatix.net
Whole thread Raw
In response to Re: allow specifying direct role membership in pg_hba.conf  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: allow specifying direct role membership in pg_hba.conf
List pgsql-hackers
On 05/17/21 17:55, Tom Lane wrote:
> This seems pretty horrid to me, not only from a complexity standpoint,
> but because it would break the principle that pg_hba.conf entries are
> applied in order.

This makes twice in a row that I've failed to see how.

If you go through the entries, in order, and simply prune from the list
the ones you can already prove would never apply to this connection, how
does that break the ordering principle?

Regards,
-Chap



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: pg_get_wal_replay_pause_state() should not return 'paused' while a promotion is ongoing.
Next
From: Peter Smith
Date:
Subject: Re: "ERROR: deadlock detected" when replicating TRUNCATE