From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Recommend include_realm=1 in docs |
Date: | 2015-05-08 23:40:45 |
Message-ID: | E1Yqrsr-0006AD-LD@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Recommend include_realm=1 in docs
As discussed, the default setting of include_realm=0 can be dangerous in
multi-realm environments because it is then impossible to differentiate
users with the same username but who are from two different realms.
Recommend include_realm=1 and note that the default setting may change
in a future version of PostgreSQL and therefore users may wish to
explicitly set include_realm to avoid issues while upgrading.
Branch
------
REL9_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/3de791ee766779f89e399da6316e0d280de6ecaa
Modified Files
--------------
doc/src/sgml/client-auth.sgml | 41 ++++++++++++++++++++++++++++++++---------
1 file changed, 32 insertions(+), 9 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-09 15:14:38 | pgsql: Improve ParseConfigFp comment wrt head/tail |
Previous Message | Stephen Frost | 2015-05-08 23:25:42 | pgsql: Modify pg_stat_get_activity to build a tuplestore |