mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Undo some poorly-thought-out "proofreading improvements".

Browse Source 
Per Tatsuhito Kasahara.
This commit is contained in:
Tom Lane 2010-10-05 18:48:13 -04:00
parent 3a13f12b3a
commit d79a1a138e
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/user-manag.sgml
View File

@ -249,11 +249,11 @@ CREATE USER <replaceable>name</replaceable>;
want to disable index scans (hint: not a good idea) anytime you want to disable index scans (hint: not a good idea) anytime you
connect, you can use: connect, you can use:
<programlisting> <programlisting>
ALTER ROLE myname SET statement_timeout = '5min'; ALTER ROLE myname SET enable_indexscan TO off;
</programlisting> </programlisting>
This will save the setting (but not set it immediately). In This will save the setting (but not set it immediately). In
subsequent connections by this role it will appear as though subsequent connections by this role it will appear as though
<literal>SET statement_timeout = '5min'</literal> had been executed <literal>SET enable_indexscan TO off</literal> had been executed
just before the session started. just before the session started.
You can still alter this setting during the session; it will only You can still alter this setting during the session; it will only
be the default. To remove a role-specific default setting, use be the default. To remove a role-specific default setting, use
@ -387,10 +387,10 @@ REVOKE <replaceable>group_role</replaceable> FROM <replaceable>role1</replaceabl
database session has access to the privileges of the group role rather database session has access to the privileges of the group role rather
than the original login role, and any database objects created are than the original login role, and any database objects created are
considered owned by the group role not the login role. Second, member considered owned by the group role not the login role. Second, member
roles that have the <literal>INHERIT</> attribute automatically inherit the roles that have the <literal>INHERIT</> attribute automatically have use
privileges of roles of which they are members, including their of the privileges of roles of which they are members, including any
<literal>INHERIT</> attributes. As an example, suppose we have privileges inherited by those roles.
done: As an example, suppose we have done:
<programlisting> <programlisting>
CREATE ROLE joe LOGIN INHERIT; CREATE ROLE joe LOGIN INHERIT;
CREATE ROLE admin NOINHERIT; CREATE ROLE admin NOINHERIT;