| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Keywords in pg_hba.conf should be field-specific |
| Date: | 2011-06-21 00:06:39 |
| Message-ID: | BANLkTimBeMZoXa1RFnc1L7PmUdL1u276qw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21 June 2011 06:06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Alvaro Herrera's message of lun jun 20 12:19:37 -0400 2011:
>> Excerpts from Pavel Stehule's message of lun jun 20 11:34:25 -0400 2011:
>>
>> > b) probably you can simplify a memory management using own two
>> > persistent memory context - and you can swap it. Then functions like
>> > free_hba_record, clean_hba_list, free_lines should be removed.
>>
>> Yeah, I reworked the patch with something like that over the weekend.
>> Not all of it though. I'll send an updated version shortly.
>
> Here it is, please let me know what you think. I took the liberty of
> cleaning up some things that were clearly historical leftovers.
>
Okay, yeah, the MemoryContext approach is far more elegant than what I
had. Boy was I ever barking up the wrong tree.
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-06-21 01:11:59 | Re: Fwd: Keywords in pg_hba.conf should be field-specific |
| Previous Message | Simon Riggs | 2011-06-20 23:03:00 | Re: ALTER TABLE lock strength reduction patch is unsafe |