Re: pg_hba_file_settings view patch

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: 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-03 04:51:50
Message-ID: CAB7nPqQ562wDzD7AqTMDsi13gzHYp=-me+rj0gPWEEx7yH59OQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 5, 2016 at 4:09 PM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> wrote:
> On Sun, Sep 4, 2016 at 1:44 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On 15 August 2016 at 12:17, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
>> wrote:
>>
>> > comments?
>>
>> This looks like a good feature contribution, thanks.
>>
>> At present the patch doesn't apply cleanly, please rebase.
>
>
> Rebased patch is attached.

Moved to next CF as there is a patch and no reviews.

+ push_jsonb_string_key(&parseState, "map");
+ push_jsonb_string_value(&parseState, hba->usermap);
[...]
+ <row>
+ <entry><structfield>options</structfield></entry>
+ <entry><type>jsonb</type></entry>
+ <entry>Configuration options set for authentication method</entry>
+ </row>
Why is it an advantage to use jsonb here instead of a simple array
made of name=value? If they were nested I'd see a case for it but it
seems to me that as presented this is just an overkill. In short, I
think that this patch needs a bit of rework, so I am marking it as
returned with feedback.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-10-03 05:01:56 Commit fest 2016-09 is now closed
Previous Message Amit Langote 2016-10-03 04:45:30 Re: Declarative partitioning - another take