| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | fabriziomello(at)gmail(dot)com |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "Prabakaran, Vaishnavi" <vaishnavip(at)fast(dot)au(dot)fujitsu(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
| Subject: | Re: Providing catalog view to pg_hba.conf file - Patch submission |
| Date: | 2015-01-28 19:27:03 |
| Message-ID: | 5661.1422473223@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= <fabriziomello(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-01-28 19:40:41 | compiler warnings in copy.c |
| Previous Message | Fabrízio de Royes Mello | 2015-01-28 19:12:24 | Re: Providing catalog view to pg_hba.conf file - Patch submission |