Re: pgsql: Make it possible to change Kerberos/GSSAPI parameters without - Mailing list pgsql-committers

From Magnus Hagander
Subject Re: pgsql: Make it possible to change Kerberos/GSSAPI parameters without
Date
Msg-id 49649E5D.3040208@hagander.net
Whole thread Raw
In response to Re: pgsql: Make it possible to change Kerberos/GSSAPI parameters without  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tom Lane wrote:
> mha@postgresql.org (Magnus Hagander) writes:
>> Log Message:
>> -----------
>> Make it possible to change Kerberos/GSSAPI parameters without restarting
>> the postmaster. They are only used in backend processes, so it's just
>> a matter of re-labeling the GUCs.
>
> Please use the appropriate phraseology for SIGHUP parameters, namely
>
>         This parameter can only be set in the <filename>postgresql.conf</>
>         file or on the server command line.

Done.

There may be a few more around that area that actually needs that done..

Being someone who really doesn't know the docbook stuff - is there any
way to "template" these things? So we could just use a custom tag that
would expand into the full set of SGML tags to document a single config
option?

//Magnus


pgsql-committers by date:

Previous
From: mha@postgresql.org (Magnus Hagander)
Date:
Subject: pgsql: Add appropriate text for SIGHUP parameters instead of just
Next
From: mha@postgresql.org (Magnus Hagander)
Date:
Subject: pgsql: Allow krb_realm (krb5, gssapi and sspi) and krb_server_hostname