| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, 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 22:55:23 |
| Message-ID: | 12968.1287269723@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Brendan Jurd's message of sb oct 16 11:53:31 -0300 2010:
>> 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?
+1. That newline thing is a crude hack and always has been. If people
are dissatisfied with it, it's time to start over rather than piling
additional crockery on top.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-16 22:59:40 | Re: Keywords in pg_hba.conf should be field-specific |
| Previous Message | Tom Lane | 2010-10-16 22:52:27 | Re: Extensions, this time with a patch |