On Wed, Jul 22, 2009 at 11:42, Peter Much<pmc@citylink.dinoex.sub.org> wrot=
e:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A04932
> Logged by: =A0 =A0 =A0 =A0 =A0Peter Much
> Email address: =A0 =A0 =A0pmc@citylink.dinoex.sub.org
> PostgreSQL version: 8.4.0
> Operating system: =A0 FreeBSD 7.2
> Description: =A0 =A0 =A0 =A0Upgrade 8.2.13 -> 8.4.0 - Kerberos option mis=
sing
> Details:
>
> In chapter 19.3.5 of the manual an option "krb_server_hostname" is
> mentioned.
> This option was present in 8.2 but is no longer present in 8.4.0
It is present, only it has now been moved to pg_hba.conf. It is no
longer in postgresql.conf. My guess is that you tried it configured
the same way as in previous versions, where there was a global
parameter in postgresql.conf?
> So at least we have a documentation bug here.
That page lists settings for pg_hba.conf, so I believe it is correct.
However, suggestions for improvements are always welcome :-)
> But the essential point seems to me the following: section 19.3.5 of the
> manual reads "hostname is the fully qualified host name of the server
> machine."
>
> But _there_is_no_such_thing_ as a "fully qualified hostname"!
> There are only _fully_qualified_interface-names_, and any host can have
> *many* of these. The hostname itself is nothing else than an arbitrary la=
bel
> for the machine, and it should never be used by networking software.
In a very large part of the cases, the fully qualified hostname will
be the same as the fully qualified interface name for the only
interface that's configured.
Anyway, the whole reason for moving the krb_server_hostname parameter
into pg_hba.conf is to make it *more* flexible to configure situations
like this.
--=20
Magnus Hagander
Self: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
