database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

doc: Fix typos and other minor issues

Browse Source 
Author: Alexander Lakhin <exclusion@gmail.com>
This commit is contained in:
Peter Eisentraut 2017-09-01 23:34:12 -04:00
parent 51daa7bdb3
commit afc58affb6
11 changed files with 14 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/catalogs.sgml
View File

@ -5385,7 +5385,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</>:<replaceable>&lt;salt&gt;<
<row>
<entry><structfield>pubname</structfield></entry>
<entry><type>Name</type></entry>
<entry><type>name</type></entry>
<entry></entry>
<entry>Name of the publication</entry>
</row>

1
doc/src/sgml/event-trigger.sgml
View File

@ -565,6 +565,7 @@
<entry align="center"><literal>X</literal></entry>
<entry align="center"><literal>-</literal></entry>
<entry align="center"><literal>-</literal></entry>
<entry align="center"></entry>
</row>
<row>
<entry align="left"><literal>CREATE USER MAPPING</literal></entry>

2
doc/src/sgml/indexam.sgml
View File

@ -559,7 +559,7 @@ amgettuple (IndexScanDesc scan,
a <structname>HeapTuple</> pointer stored at <literal>scan-&gt;xs_hitup</>,
with tuple descriptor <literal>scan-&gt;xs_hitupdesc</>. (The latter
format should be used when reconstructing data that might possibly not fit
into an IndexTuple.) In either case,
into an <structname>IndexTuple</>.) In either case,
management of the data referenced by the pointer is the access method's
responsibility. The data must remain good at least until the next
<function>amgettuple</>, <function>amrescan</>, or <function>amendscan</>

2
doc/src/sgml/logicaldecoding.sgml
View File

@ -345,7 +345,7 @@ $ pg_recvlogical -d postgres --slot test --drop-slot
<para>
The <link linkend="view-pg-replication-slots"><structname>pg_replication_slots</structname></link>
view and the
<link linkend="monitoring-stats-views-table"><structname>pg_stat_replication</structname></link>
<link linkend="pg-stat-replication-view"><structname>pg_stat_replication</structname></link>
view provide information about the current state of replication slots and
streaming replication connections respectively. These views apply to both physical and
logical replication.

2
doc/src/sgml/perform.sgml
View File

@ -1840,7 +1840,7 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
<listitem>
<para>
Increase <xref linkend="guc-max-wal-size"> and <xref
linkend="guc-checkpoint-timeout"> ; this reduces the frequency
linkend="guc-checkpoint-timeout">; this reduces the frequency
of checkpoints, but increases the storage requirements of
<filename>/pg_wal</>.
</para>

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

@ -89,7 +89,7 @@ ALTER SEQUENCE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> S
The optional
clause <literal>AS <replaceable class="parameter">data_type</replaceable></literal>
changes the data type of the sequence. Valid types are
are <literal>smallint</literal>, <literal>integer</literal>,
<literal>smallint</literal>, <literal>integer</literal>,
and <literal>bigint</literal>.
</para>

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

@ -620,8 +620,8 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
<literal>SHARE UPDATE EXCLUSIVE</literal> lock will be taken for
fillfactor and autovacuum storage parameters, as well as the
following planner related parameters:
effective_io_concurrency, parallel_workers, seq_page_cost
random_page_cost, n_distinct and n_distinct_inherited.
<varname>effective_io_concurrency</>, <varname>parallel_workers</>, <varname>seq_page_cost</>,
<varname>random_page_cost</>, <varname>n_distinct</> and <varname>n_distinct_inherited</>.
</para>
<note>

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

@ -482,7 +482,7 @@ COPY <replaceable class="parameter">count</replaceable>
<para>
For identity columns, the <command>COPY FROM</command> command will always
write the column values provided in the input data, like
the <command>INPUT</command> option <literal>OVERRIDING SYSTEM
the <command>INSERT</command> option <literal>OVERRIDING SYSTEM
VALUE</literal>.
</para>

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

@ -119,7 +119,7 @@ SELECT * FROM <replaceable>name</replaceable>;
The optional
clause <literal>AS <replaceable class="parameter">data_type</replaceable></literal>
specifies the data type of the sequence. Valid types are
are <literal>smallint</literal>, <literal>integer</literal>,
<literal>smallint</literal>, <literal>integer</literal>,
and <literal>bigint</literal>. <literal>bigint</literal> is the
default. The data type determines the default minimum and maximum
values of the sequence.

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

@ -473,8 +473,8 @@ FROM ( { <replaceable class="PARAMETER">numeric_literal</replaceable> | <replace
<firstterm>partitioned</firstterm> table. The parenthesized list of
columns or expressions forms the <firstterm>partition key</firstterm>
for the table. When using range partitioning, the partition key can
include multiple columns or expressions (up to 32, but this limit can
altered when building <productname>PostgreSQL</productname>.), but for
include multiple columns or expressions (up to 32, but this limit can be
altered when building <productname>PostgreSQL</productname>), but for
list partitioning, the partition key must consist of a single column or
expression. If no B-tree operator class is specified when creating a
partitioned table, the default B-tree operator class for the datatype will

4
doc/src/sgml/release-10.sgml
View File

@ -2905,7 +2905,7 @@
-->
<para>
Overhaul documentation <link linkend="docguide-toolsets">build
process</> (Alexander Lakhin, Alexander Law)
process</> (Alexander Lakhin)
</para>
</listitem>
@ -2919,7 +2919,7 @@
</para>
<para>
Previously <application>Jade</>, <acronym>DSSSL,</> and
Previously <application>Jade</>, <acronym>DSSSL</>, and
<application>JadeTex</> were used.
</para>
</listitem>