| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Brendan Jurd <direvus(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Keywords in pg_hba.conf should be field-specific |
| Date: | 2010-10-16 15:27:17 |
| Message-ID: | 1287242720-sup-7900@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Brendan Jurd's message of sáb oct 16 11:53:31 -0300 2010:
> On 17 October 2010 01:52, Brendan Jurd <direvus(at)gmail(dot)com> wrote:
> > Per the above discussion, I've prepared a patch to make keywords in
> > pg_hba.conf field-specific.
>
> Try New and Improved This Message (tm), now with attachment!
Hmm. Would it be possible to list keywords _applicable_ to each field,
and have these passed down to next_token by the caller instead? This
seems backwards, but I'm not sure if the other way is really workable.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-10-16 15:29:39 | Re: No hash join across partitioned tables? |
| Previous Message | Alvaro Herrera | 2010-10-16 15:22:02 | Re: knngist plans |