Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1soCVM-0097kR-7t for pgsql-general@arkaria.postgresql.org; Wed, 11 Sep 2024 01:50:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1soCVL-006Mcu-3N for pgsql-general@arkaria.postgresql.org; Wed, 11 Sep 2024 01:50:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1soCVK-006Mcj-9C for pgsql-general@lists.postgresql.org; Wed, 11 Sep 2024 01:50:46 +0000 Received: from [173.162.1.217] (helo=mail.tclc.org) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1soCVE-000Yqy-8L for pgsql-general@lists.postgresql.org; Wed, 11 Sep 2024 01:50:44 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.tclc.org (Postfix) with ESMTP id 4DCF3300C9E; Tue, 10 Sep 2024 18:50:36 -0700 (PDT) Received: from mail.tclc.org ([127.0.0.1]) by localhost (mail.tclc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 1TA0M5tA_9X1; Tue, 10 Sep 2024 18:50:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.tclc.org (Postfix) with ESMTP id EF00F300CB8; Tue, 10 Sep 2024 18:50:35 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.tclc.org EF00F300CB8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tryx.org; s=dkim.tryx; t=1726019436; bh=7eVPpmlsVB8rnKuU7MkWN5rIbXvdO2psmvHAIyAh3V0=; h=Date:From:To:Message-ID:MIME-Version; b=uiMPME5E2oOl21P6XZQAupzR/GP7qweLNL0NEFe2wHKKOVcA0WcgefzVYIGwhSHtb +li0rVPduw6lTUQG6e41wg5jy4fq9KmQ2k4i+fZ774KC9nfzSE7Rh6e2snL2IgECDu jabZ1ek9Gzlm4Ei4qfABuzagZSJyqlRW7aVzUYDFAHy4+voYJat3VuHG4IOs13GroO /7xnKIB3h4jtMVO1e+dakFFd4dT1FlW6AlScG387dzcuvnKeieesZGKOxX88tssTJ2 6cnQs999fmgSg2a61CPR4ipFx/yWXeefHlBTJOhfCpwSOFwpWzwZHbwn7TAGbYM4kv YJ9+It/OVeCsA== X-Virus-Scanned: amavisd-new at tclc.org Received: from mail.tclc.org ([127.0.0.1]) by localhost (mail.tclc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id WyKwAMfJSQlY; Tue, 10 Sep 2024 18:50:35 -0700 (PDT) Received: from mail.tclc.org (mail.tryx.tclc.org [10.1.1.12]) by mail.tclc.org (Postfix) with ESMTP id C9873300C9E; Tue, 10 Sep 2024 18:50:35 -0700 (PDT) Date: Tue, 10 Sep 2024 18:50:35 -0700 (PDT) From: Chris Miller Reply-To: Chris Miller To: "David G. Johnston" Cc: pgsql-general Message-ID: <413962829.8625.1726019435545.JavaMail.zimbra@tryx.org> In-Reply-To: References: <172601029329.1028.17318986799853058856@malur.postgresql.org> <1738731565.8400.1726010470879.JavaMail.zimbra@tryx.org> Subject: Re: Test mail for pgsql-general MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_f826e92d-a962-4449-a1ee-fa4b0f6b3b6a" X-Originating-IP: [10.1.1.12] X-Mailer: Zimbra 8.8.15_GA_4484 (ZimbraWebClient - FF130 (Linux)/8.8.15_GA_4481) Thread-Topic: Test mail for pgsql-general Thread-Index: eMfcemiBXKgw3KHhs0DxAqBWDCcXKA== X-Host-Lookup-Failed: Reverse DNS lookup failed for 173.162.1.217 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_f826e92d-a962-4449-a1ee-fa4b0f6b3b6a Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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. --=_f826e92d-a962-4449-a1ee-fa4b0f6b3b6a Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi David,
The second line is pointless, the first three columns are compared agains= t the incoming connection host/user/dbname to find out how authentication s= hould be handled.  The first match wins.  So for every local conn= ection peer, and only peer, is going to be used since everything matches al= l/all.

There is no way to give a user a choice of how to auth= enticate.  There will be one accepted option for a given set of connec= tion values.
This answers my question. Th= anks for the help,
--
Chris.
<= /body> --=_f826e92d-a962-4449-a1ee-fa4b0f6b3b6a--