Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YGYGw-0005OG-Ko for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Jan 2015 19:27:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YGYGv-0007NE-TQ for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Jan 2015 19:27:29 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YGYGu-0007MZ-GY for pgsql-hackers@postgresql.org; Wed, 28 Jan 2015 19:27:28 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YGYGr-0000ck-Ht for pgsql-hackers@postgresql.org; Wed, 28 Jan 2015 19:27:26 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t0SJR3s0005662; Wed, 28 Jan 2015 14:27:03 -0500 From: Tom Lane To: fabriziomello@gmail.com cc: Haribabu Kommi , Jim Nasby , Abhijit Menon-Sen , "pgsql-hackers@postgresql.org" , "Prabakaran, Vaishnavi" , Magnus Hagander , Jaime Casanova Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission In-reply-to: References: <82897A1301080E4B8E461DDAA0FFCF14DDE1@SYD1216> <82897A1301080E4B8E461DDAA0FFCF14FD6E@SYD1216> <20140629165554.GA5984@toroid.org> <20140630070646.GY31357@toroid.org> <54C8156E.1080500@BlueTreble.com> Comments: In-reply-to =?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= message dated "Wed, 28 Jan 2015 17:12:24 -0200" Date: Wed, 28 Jan 2015 14:27:03 -0500 Message-ID: <5661.1422473223@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org =?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= writes: > But I'm thinking about this patch and would not be interesting to have a > FDW to manipulate the hba file? Imagine if we are able to manipulate the > HBA file using INSERT/UPDATE/DELETE. Since the HBA file is fundamentally order-dependent, while SQL tables are fundamentally not, that doesn't seem like a great API match. You could probably brute-force something that would work, but it would very much be a case of using a hammer to solve a screwdriver problem. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers