Re: Make hba available to client code

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make hba available to client code
Date: 2015-01-28 21:10:42
Message-ID: 7899.1422479442@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter <david(at)fetter(dot)org> writes:
> While investigating another project, namely adding pg_hba.conf support
> to pgbouncer, I ran into a stumbling block others probably will, too:
> the hba code is backend-only, which means that if I were to do this
> as-is, I would be cooking a batch of very unappetizing copypasta.

> I'm allergic to copypasta, so unless there are big objections, I'd
> like to export those functions to make hba available to other code.

How exactly would exporting those functions help anything client-side?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-01-28 21:13:47 Re: jsonb, unicode escapes and escaped backslashes
Previous Message Tomas Vondra 2015-01-28 20:56:00 Re: PATCH: decreasing memory needlessly consumed by array_agg