Magnus Hagander <[EMAIL PROTECTED]> 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
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
