@@ -129,7 +129,7 @@ SELECT rolname FROM pg_roles;
129129 is determined by the client authentication setup, as explained in
130130 <xref linkend="client-authentication">. (Thus, a client is not
131131 limited to connect as the role matching
132- its operating system user, just as a person's login name
132+ its operating system user, just as a person's login name
133133 need not match her real name.) Since the role
134134 identity determines the set of privileges available to a connected
135135 client, it is important to carefully configure privileges when setting up
@@ -219,7 +219,7 @@ CREATE USER <replaceable>name</replaceable>;
219219 make use of passwords. Database passwords are separate from
220220 operating system passwords. Specify a password upon role
221221 creation with <literal>CREATE ROLE
222- <replaceable>name</replaceable> PASSWORD '<replaceable>string</>'</literal>.
222+ <replaceable>name</replaceable> PASSWORD '<replaceable>string</>'</literal>.
223223 </para>
224224 </listitem>
225225 </varlistentry>
@@ -249,11 +249,11 @@ CREATE USER <replaceable>name</replaceable>;
249249 want to disable index scans (hint: not a good idea) anytime you
250250 connect, you can use:
251251<programlisting>
252- ALTER ROLE myname SETstatement_timeout = '5min' ;
252+ ALTER ROLE myname SETenable_indexscan TO off ;
253253</programlisting>
254254 This will save the setting (but not set it immediately). In
255255 subsequent connections by this role it will appear as though
256- <literal>SETstatement_timeout = '5min' </literal> had been executed
256+ <literal>SETenable_indexscan TO off </literal> had been executed
257257 just before the session started.
258258 You can still alter this setting during the session; it will only
259259 be the default. To remove a role-specific default setting, use
@@ -387,10 +387,10 @@ REVOKE <replaceable>group_role</replaceable> FROM <replaceable>role1</replaceabl
387387 database session has access to the privileges of the group role rather
388388 than the original login role, and any database objects created are
389389 considered owned by the group role not the login role. Second, member
390- roles that have the <literal>INHERIT</> attribute automaticallyinherit the
391- privileges of roles of which they are members, includingtheir
392- <literal>INHERIT</> attributes. As an example, suppose we have
393- done:
390+ roles that have the <literal>INHERIT</> attribute automaticallyhave use
391+ of the privileges of roles of which they are members, includingany
392+ privileges inherited by those roles.
393+ As an example, suppose we have done:
394394<programlisting>
395395CREATE ROLE joe LOGIN INHERIT;
396396CREATE ROLE admin NOINHERIT;