database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

Don't use SGML empty tags

Browse Source 
For DocBook XML compatibility, don't use SGML empty tags (</>) anymore,
replace by the full tag name.  Add a warning option to catch future
occurrences.

Alexander Lakhin, Jürgen Purtz
This commit is contained in:
Peter Eisentraut
2017-10-08 21:44:17 -04:00
parent 6ecabead4b
commit c29c578908
337 changed files with 31636 additions and 31635 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/src/sgml/ref/set_session_auth.sgml
View File

@ -39,7 +39,7 @@ RESET SESSION AUTHORIZATION
The session user identifier is initially set to be the (possibly
authenticated) user name provided by the client. The current user
identifier is normally equal to the session user identifier, but
might change temporarily in the context of <literal>SECURITY DEFINER</>
might change temporarily in the context of <literal>SECURITY DEFINER</literal>
functions and similar mechanisms; it can also be changed by
<xref linkend="sql-set-role">.
The current user identifier is relevant for permission checking.
@ -53,13 +53,13 @@ RESET SESSION AUTHORIZATION
</para>
<para>
The <literal>SESSION</> and <literal>LOCAL</> modifiers act the same
The <literal>SESSION</literal> and <literal>LOCAL</literal> modifiers act the same
as for the regular <xref linkend="SQL-SET">
command.
</para>
<para>
The <literal>DEFAULT</> and <literal>RESET</> forms reset the session
The <literal>DEFAULT</literal> and <literal>RESET</literal> forms reset the session
and current user identifiers to be the originally authenticated user
name. These forms can be executed by any user.
</para>
@ -69,8 +69,8 @@ RESET SESSION AUTHORIZATION
<title>Notes</title>
<para>
<command>SET SESSION AUTHORIZATION</> cannot be used within a
<literal>SECURITY DEFINER</> function.
<command>SET SESSION AUTHORIZATION</command> cannot be used within a
<literal>SECURITY DEFINER</literal> function.
</para>
</refsect1>
@ -101,13 +101,13 @@ SELECT SESSION_USER, CURRENT_USER;
The SQL standard allows some other expressions to appear in place
of the literal <replaceable>user_name</replaceable>, but these options
are not important in practice. <productname>PostgreSQL</productname>
allows identifier syntax (<literal>"<replaceable>username</>"</literal>), which SQL
allows identifier syntax (<literal>"<replaceable>username</replaceable>"</literal>), which SQL
does not. SQL does not allow this command during a transaction;
<productname>PostgreSQL</productname> does not make this
restriction because there is no reason to.
The <literal>SESSION</> and <literal>LOCAL</> modifiers are a
The <literal>SESSION</literal> and <literal>LOCAL</literal> modifiers are a
<productname>PostgreSQL</productname> extension, as is the
<literal>RESET</> syntax.
<literal>RESET</literal> syntax.
</para>
<para>