Skip site navigation (1) Skip section navigation (2)

Re: Parsing errors in pg_hba.conf

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing errors in pg_hba.conf
Date: 2008-10-27 14:37:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> 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 ;-)

:-) THat's what I was guessing.

Anyway, here's what I intended:


Attachment: hba.diff
Description: text/x-diff (5.7 KB)

In response to

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2008-10-27 15:03:06
Subject: Re: Making pg_standby compression-friendly
Previous:From: Jonah H. HarrisDate: 2008-10-27 14:36:55
Subject: Re: SQL/MED compatible connection manager

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group