Re: pg_hba.conf - patch to report all parsing errors, and then bail

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Selena Deckelmann <selena(at)endpoint(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_hba.conf - patch to report all parsing errors, and then bail
Date: 2009-03-07 18:49:17
Message-ID: 49B2C1AD.9070805@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Selena Deckelmann <selena(at)endpoint(dot)com> writes:
>> Currently, load_hba() bails on the first parsing error. It would be
>> better for the typo-prone sysadmin if it reported ALL errors, and THEN
>> bailed out.
>
>> This patch implements that behavior. Tested against 8.4 HEAD this morning.
>
> It sure looks like that's going to try to free new_parsed_lines more
> than once. Shouldn't clean_hba_list be done just once?

Yeah, it should be done in the if branch down below. And I think by our
coding standards (or at least by our conventions), the variable should
be "ok" and not "OK".

Unless there are any objections, I can do those cleanups and apply it.

//Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-03-07 18:51:49 Re: pg_hba.conf - patch to report all parsing errors, and then bail
Previous Message Tom Lane 2009-03-07 18:28:32 Re: pg_hba.conf - patch to report all parsing errors, and then bail