Re: pg_hba_lookup function to get all matching pg_hba.conf entries - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: pg_hba_lookup function to get all matching pg_hba.conf entries
Date
Msg-id CAA4eK1LmMu=Qb0jbNX8-8dcbEPbuu9XKPP1k-6_q7eUfYUDrDw@mail.gmail.com
Whole thread Raw
In response to Re: pg_hba_lookup function to get all matching pg_hba.conf entries  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: pg_hba_lookup function to get all matching pg_hba.conf entries  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
On Thu, Dec 10, 2015 at 9:51 AM, Haribabu Kommi <kommi.haribabu@gmail.com> wrote:
>
> On Thu, Dec 10, 2015 at 2:29 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:

> > How about creating "hba parser context" and "ident parser context"
> > at the beginning of their respective functions and don't change
> > anything in tokenize_file()?
>
> The tokenize file cxt is deleted after a successful load of pg_hba.conf or
> pg_ident.conf files. we don't need this memory once the pg_hba.conf
> or pg_ident file is loaded, because of this reason, it is created as a
> separate context and deleted later.
>

What about the error case?


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: parallel joins, and better parallel explain
Next
From: Michael Paquier
Date:
Subject: Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.