Re: Parsing errors in pg_hba.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing errors in pg_hba.conf
Date: 2008-10-27 13:25:28
Message-ID: 15319.1225113928@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Tom Lane wrote:
>> It would be seriously messy to try to make the parse-error code know
>> about things like that. Better would be to keep the GUC variable in
>> existence always and have an assign hook to throw the error.

> Um, no, it wouldn't :-) At least that's my impression. We're only
> talking a bout the pg_hba code.

Oh, sorry, for some reason I read this as postgresql.conf parsing.
Too early in the morning, need more caffeine ;-)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2008-10-27 13:54:40 Re: WIP patch: convert SQL-language functions to return tuplestores
Previous Message Alvaro Herrera 2008-10-27 13:01:48 Re: WIP: default values for function parameters