| From: | Chris Miller <cjm(at)tryx(dot)org> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Test mail for pgsql-general |
| Date: | 2024-09-11 01:50:35 |
| Message-ID: | 413962829.8625.1726019435545.JavaMail.zimbra@tryx.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi David,
> The second line is pointless, the first three columns are compared against the
> incoming connection host/user/dbname to find out how authentication should be
> handled. The first match wins. So for every local connection peer, and only
> peer, is going to be used since everything matches all/all.
> There is no way to give a user a choice of how to authenticate. There will be
> one accepted option for a given set of connection values.
This answers my question. Thanks for the help,
--
Chris.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Miller | 2024-09-11 01:51:41 | Re: Test mail for pgsql-general |
| Previous Message | Erik Wienhold | 2024-09-10 23:34:21 | Re: Removing duplicate rows in table |