We have modified your patch and it will appear in 8.1. Thanks.
---
Daniel Ahlin wrote:
> Hi
>
> This is a two part patch against 7.4.5 implementing the option of
> configuring what is now set using the #defined constant PG
Even though I am unsure about the feature addition, I am keeping this
for 8.1 in case someone else finds it useful.
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Danie
No one has ever asked for a kerberos service name different from
"postgres". Unless someone else says this is a useful feature, I
think we are better off leaving our code unchanged.
Kerberos is pretty complicated so adding another configuration options
isn't always a good idea.
Tom Lane <[EMAIL PROTECTED]> writes:
> Daniel Ahlin <[EMAIL PROTECTED]> writes:
> > This is a two part patch against 7.4.5 implementing the option of
> > configuring what is now set using the #defined constant PG_KRB_SRVNAM
> > (the name of the service part of the kerberos principal the server
> >
Daniel Ahlin <[EMAIL PROTECTED]> writes:
> This is a two part patch against 7.4.5 implementing the option of
> configuring what is now set using the #defined constant PG_KRB_SRVNAM
> (the name of the service part of the kerberos principal the server
> uses).
Is this a good idea? Offhand it just s
Hi
This is a two part patch against 7.4.5 implementing the option of
configuring what is now set using the #defined constant PG_KRB_SRVNAM
(the name of the service part of the kerberos principal the server
uses).
On the backend it can be configured by the (new) string option
krb_srvnam in postgre
