| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_hba_file_settings view patch |
| Date: | 2016-10-26 19:54:22 |
| Message-ID: | 3759eba9-0f44-d01f-872c-16a3eaeabc07@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/26/2016 12:24 PM, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> FWIW, I'm -1 on using JSON here. I don't believe that we should start
>> using JSON all over the place just because we can. If we do that,
>> we'll end up with a mishmash of styles, and maybe look silly when JSON
>> is replaced by the new and much better SDGJHSDR format.
>
> I concur. JSON isn't a core datatype and I don't want to see it treated
> as one. We should redesign this view so that it doesn't rely on anything
> more advanced than arrays.
Huh? Sure it is. Ships in PostgreSQL-core.
I mean, I'm not particularly in favor of using JSON for this (arrays
seem OK), but that seems like an invalid reason not to.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2016-10-26 20:04:15 | Re: pg_hba_file_settings view patch |
| Previous Message | Thomas Munro | 2016-10-26 19:46:14 | Re: Default setting for autovacuum_freeze_max_age |