On 10/2/16, Michael Paquier <michael.paqu...@gmail.com> wrote: > + 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.
I guess for ability to use filtering like: SELECT * FROM pg_hba_rules WHERE options->>radiusserver LIKE '%.example.com'; I think it would be harder if options is an array of strings... -- Best regards, Vitaly Burovoy -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
