Re: pg_hba_file_settings view patch - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_hba_file_settings view patch
Date
Msg-id 20161027171707.xinbr57gbyepn73r@alvherre.pgsql
Whole thread Raw
In response to Re: pg_hba_file_settings view patch  (Greg Stark <stark@mit.edu>)
Responses Re: pg_hba_file_settings view patch  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
Greg Stark wrote:

> The fundamental problem is that the pga_hba.conf file has some bits of
> complex structure that aren't easily captured by linear arrays. The
> problem I struggled with most was the keywords like "all", "samerole",
> and "replication". A simple array of text makes it awkward to
> distinguish those keywords from the quoted text values with the same
> content. And then there are the ldap options which naturally would be
> a data type like json or htab.

Hmm I thought we had decided that such keywords would live in separate
arrays, i.e. you have one array for plain names and another array for
keyword stuff.  Then it's not ambiguous anymore.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: condition variables
Next
From: "Karl O. Pinc"
Date:
Subject: Re: Patch to implement pg_current_logfile() function