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:
Description: text/x-diff (5.7 KB)
In response to
pgsql-hackers by date
|Next:||From: Kevin Grittner||Date: 2008-10-27 15:03:06|
|Subject: Re: Making pg_standby compression-friendly|
|Previous:||From: Jonah H. Harris||Date: 2008-10-27 14:36:55|
|Subject: Re: SQL/MED compatible connection manager|