From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
Subject: | Re: Including kerberos realm |
Date: | 2009-01-07 12:39:17 |
Message-ID: | 4964A275.40009@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Alvaro Herrera wrote:
>>> Not that this affects me in any way, but should there be a GUC variable
>>> to set the default behavior system-wide?
>
>> I thought about that, but I don't want to add extra gucs without a good
>> reason. You'd typically not have very many different lines in pg_hba for
>> this, and just duplicating the parameter there would be ok I think.
>
>> I'd rather move more of the krb parameters to be *just* in pg_hba.conf,
>> but for now I left those in postgresql.conf as fallbacks..
>
> If you think those parameters would make more sense in pg_hba.conf,
> let's just move them and be done with it. There has never been any
> intention that administrator-only GUCs would be promised compatible
> across versions. And the GUC mechanism is really rather a lot of
> overhead compared to options on a pg_hba line ...
Well, it does make sense to have defaults in postgresql.conf - but I
don't think it's worth the overhead.
I'll commit the stuff I have for now and put it on my TODO to remove
them completely from postgresql.conf later. I'll see if I have time to
get it done for 8.4.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-01-07 12:41:03 | Re: dblink vs SQL/MED - security and implementation details |
Previous Message | Simon Riggs | 2009-01-07 12:23:46 | Re: Latest version of Hot Standby patch |