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 1qoAma-000OA3-GM for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Oct 2023 22:55:56 +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 1qoAmX-006Eqx-Fo for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Oct 2023 22:55:54 +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 1qoAmX-006Eqp-5j for pgsql-hackers@lists.postgresql.org; Wed, 04 Oct 2023 22:55:54 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qoAmV-0004N4-Ey for pgsql-hackers@lists.postgresql.org; Wed, 04 Oct 2023 22:55:53 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 394MtiJG2647174; Wed, 4 Oct 2023 18:55:44 -0400 From: Tom Lane To: Robert Haas cc: Jim Jones , PostgreSQL Hackers , Daniel Gustafsson , Peter Eisentraut Subject: Re: Add annotation syntax to pg_hba.conf entries In-reply-to: References: <997377b9-b2c7-452d-75af-eca6668d6e77@uni-muenster.de> Comments: In-reply-to Robert Haas message dated "Wed, 04 Oct 2023 16:18:50 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2647172.1696460144.1@sss.pgh.pa.us> Date: Wed, 04 Oct 2023 18:55:44 -0400 Message-ID: <2647173.1696460144@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > You're probably not going to like this answer very much, but this > doesn't seem particularly worthwhile to me. Yeah, I was unconvinced about the number of use-cases too. As you say, some support from other potential users could convince me otherwise, but right now the evidence seems thin. > The argument for this > feature is not that this information needs to exist, but that it needs > to be queryable from within PostgreSQL. Not only that, but that it needs to be accessible via the pg_hba_file_rules view. Superusers could already see the pg_hba file's contents via pg_read_file(). Again, that's not an argument that this is a bad idea. But it's an answer that would likely satisfy some fraction of whatever potential users are out there, which makes the question of how many use-cases really exist even more pressing. regards, tom lane