sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-31 00:03:57 -04:00
Code Issues Projects Releases Wiki Activity

Replace single-quotes with double-quotes in a few SGML attributes.

Browse Source 
Both are valid SGML, but let's be consistent.

Author: Peter Smith
Discussion: https://www.postgresql.org/message-id/CAHut%2BPtghjg0SBUTv%3D4Bpcy68d1zD3VAnZ3wX1DQSp39XKD9Sw%40mail.gmail.com
This commit is contained in:
Heikki Linnakangas 2023-02-27 09:55:39 +02:00
parent 0a0500207a
commit 46647cc4b8
6 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/libpq.sgml
View File

@ -1736,8 +1736,8 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname
revocation list (CRL). Certificates listed in this file, if it
exists, will be rejected while attempting to authenticate the
server's certificate. If neither
<xref linkend='libpq-connect-sslcrl'/> nor
<xref linkend='libpq-connect-sslcrldir'/> is set, this setting is
<xref linkend="libpq-connect-sslcrl"/> nor
<xref linkend="libpq-connect-sslcrldir"/> is set, this setting is
taken as
<filename>~/.postgresql/root.crl</filename>.
</para>

14
doc/src/sgml/monitoring.sgml
View File

@ -372,7 +372,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
<entry><structname>pg_stat_progress_analyze</structname><indexterm><primary>pg_stat_progress_analyze</primary></indexterm></entry>
<entry>One row for each backend (including autovacuum worker processes) running
<command>ANALYZE</command>, showing current progress.
See <xref linkend='analyze-progress-reporting'/>.
See <xref linkend="analyze-progress-reporting"/>.
</entry>
</row>
@ -380,7 +380,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
<entry><structname>pg_stat_progress_create_index</structname><indexterm><primary>pg_stat_progress_create_index</primary></indexterm></entry>
<entry>One row for each backend running <command>CREATE INDEX</command> or <command>REINDEX</command>, showing
current progress.
See <xref linkend='create-index-progress-reporting'/>.
See <xref linkend="create-index-progress-reporting"/>.
</entry>
</row>
@ -388,7 +388,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
<entry><structname>pg_stat_progress_vacuum</structname><indexterm><primary>pg_stat_progress_vacuum</primary></indexterm></entry>
<entry>One row for each backend (including autovacuum worker processes) running
<command>VACUUM</command>, showing current progress.
See <xref linkend='vacuum-progress-reporting'/>.
See <xref linkend="vacuum-progress-reporting"/>.
</entry>
</row>
@ -396,7 +396,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
<entry><structname>pg_stat_progress_cluster</structname><indexterm><primary>pg_stat_progress_cluster</primary></indexterm></entry>
<entry>One row for each backend running
<command>CLUSTER</command> or <command>VACUUM FULL</command>, showing current progress.
See <xref linkend='cluster-progress-reporting'/>.
See <xref linkend="cluster-progress-reporting"/>.
</entry>
</row>
@ -404,14 +404,14 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
<entry><structname>pg_stat_progress_basebackup</structname><indexterm><primary>pg_stat_progress_basebackup</primary></indexterm></entry>
<entry>One row for each WAL sender process streaming a base backup,
showing current progress.
See <xref linkend='basebackup-progress-reporting'/>.
See <xref linkend="basebackup-progress-reporting"/>.
</entry>
</row>
<row>
<entry><structname>pg_stat_progress_copy</structname><indexterm><primary>pg_stat_progress_copy</primary></indexterm></entry>
<entry>One row for each backend running <command>COPY</command>, showing current progress.
See <xref linkend='copy-progress-reporting'/>.
See <xref linkend="copy-progress-reporting"/>.
</entry>
</row>
</tbody>
@ -7055,7 +7055,7 @@ FROM pg_stat_get_backend_idset() AS backendid;
<structname>pg_stat_progress_cluster</structname>
because both <command>VACUUM FULL</command> and <command>CLUSTER</command>
rewrite the table, while regular <command>VACUUM</command> only modifies it
in place. See <xref linkend='cluster-progress-reporting'/>.
in place. See <xref linkend="cluster-progress-reporting"/>.
</para>
<table id="pg-stat-progress-vacuum-view" xreflabel="pg_stat_progress_vacuum">

2
doc/src/sgml/ref/create_role.sgml
View File

@ -123,7 +123,7 @@ in sync when changing the above synopsis!
These clauses determine whether a role will be permitted to
create, alter, drop, comment on, and change the security label for
other roles.
See <xref linkend='role-creation' /> for more details about what
See <xref linkend="role-creation"/> for more details about what
capabilities are conferred by this privilege.
If not specified, <literal>NOCREATEROLE</literal> is the default.
</para>

4
doc/src/sgml/ref/createuser.sgml
View File

@ -48,7 +48,7 @@ PostgreSQL documentation
Being a superuser implies the ability to bypass all access permission
checks within the database, so superuser access should not be granted
lightly. <literal>CREATEROLE</literal> also conveys
<link linkend='role-creation'>very extensive privileges</link>.
<link linkend="role-creation">very extensive privileges</link>.
</para>
<para>
@ -254,7 +254,7 @@ PostgreSQL documentation
The new user will be allowed to create, alter, drop, comment on,
change the security label for other roles; that is,
this user will have <literal>CREATEROLE</literal> privilege.
See <xref linkend='role-creation' /> for more details about what
See <xref linkend="role-creation"/> for more details about what
capabilities are conferred by this privilege.
</para>
</listitem>

6
doc/src/sgml/ref/pgbench.sgml
View File

@ -1167,7 +1167,7 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>d
</para>
<variablelist>
<varlistentry id='pgbench-metacommand-gset'>
<varlistentry id="pgbench-metacommand-gset">
<term>
<literal>\gset [<replaceable>prefix</replaceable>]</literal>
<literal>\aset [<replaceable>prefix</replaceable>]</literal>
@ -1237,7 +1237,7 @@ SELECT 4 AS four \; SELECT 5 AS five \aset
</listitem>
</varlistentry>
<varlistentry id='pgbench-metacommand-set'>
<varlistentry id="pgbench-metacommand-set">
<term>
<literal>\set <replaceable>varname</replaceable> <replaceable>expression</replaceable></literal>
</term>
@ -1362,7 +1362,7 @@ SELECT 4 AS four \; SELECT 5 AS five \aset
</listitem>
</varlistentry>
<varlistentry id='pgbench-metacommand-pipeline'>
<varlistentry id="pgbench-metacommand-pipeline">
<term><literal>\startpipeline</literal></term>
<term><literal>\endpipeline</literal></term>

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

@ -191,7 +191,7 @@ CREATE USER <replaceable>name</replaceable>;
</varlistentry>
<varlistentry>
<term id='role-creation'>role creation<indexterm><primary>role</primary><secondary>privilege to create</secondary></indexterm></term>
<term id="role-creation">role creation<indexterm><primary>role</primary><secondary>privilege to create</secondary></indexterm></term>
<listitem>
<para>
A role must be explicitly given permission to create more roles