doc: Fix some grammar and inconsistencies
Some comments are fixed while on it. Author: Justin Pryzby Discussion: https://postgr.es/m/20200818171702.GK17022@telsasoft.com Backpatch-through: 9.6
This commit is contained in:
parent
fe4d022c8e
commit
aad546bd0a
@ -223,7 +223,7 @@ $ pg_recvlogical -d postgres --slot=test --drop-slot
|
|||||||
A logical slot will emit each change just once in normal operation.
|
A logical slot will emit each change just once in normal operation.
|
||||||
The current position of each slot is persisted only at checkpoint, so in
|
The current position of each slot is persisted only at checkpoint, so in
|
||||||
the case of a crash the slot may return to an earlier LSN, which will
|
the case of a crash the slot may return to an earlier LSN, which will
|
||||||
then cause recent changes to be resent when the server restarts.
|
then cause recent changes to be sent again when the server restarts.
|
||||||
Logical decoding clients are responsible for avoiding ill effects from
|
Logical decoding clients are responsible for avoiding ill effects from
|
||||||
handling the same message more than once. Clients may wish to record
|
handling the same message more than once. Clients may wish to record
|
||||||
the last LSN they saw when decoding and skip over any repeated data or
|
the last LSN they saw when decoding and skip over any repeated data or
|
||||||
|
@ -889,7 +889,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
|
|||||||
from the parent table will be created in the partition, if they don't
|
from the parent table will be created in the partition, if they don't
|
||||||
already exist.
|
already exist.
|
||||||
If any of the <literal>CHECK</literal> constraints of the table being
|
If any of the <literal>CHECK</literal> constraints of the table being
|
||||||
attached is marked <literal>NO INHERIT</literal>, the command will fail;
|
attached are marked <literal>NO INHERIT</literal>, the command will fail;
|
||||||
such constraints must be recreated without the
|
such constraints must be recreated without the
|
||||||
<literal>NO INHERIT</literal> clause.
|
<literal>NO INHERIT</literal> clause.
|
||||||
</para>
|
</para>
|
||||||
|
@ -160,7 +160,7 @@ CREATE SUBSCRIPTION <replaceable class="parameter">subscription_name</replaceabl
|
|||||||
<para>
|
<para>
|
||||||
It is safe to use <literal>off</literal> for logical replication:
|
It is safe to use <literal>off</literal> for logical replication:
|
||||||
If the subscriber loses transactions because of missing
|
If the subscriber loses transactions because of missing
|
||||||
synchronization, the data will be resent from the publisher.
|
synchronization, the data will be sent again from the publisher.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
@ -82,8 +82,8 @@ PostgreSQL documentation
|
|||||||
for any files for which the computed checksum does not match the
|
for any files for which the computed checksum does not match the
|
||||||
checksum stored in the manifest. This step is not performed for any files
|
checksum stored in the manifest. This step is not performed for any files
|
||||||
which produced errors in the previous step, since they are already known
|
which produced errors in the previous step, since they are already known
|
||||||
to have problems. Also, files which were ignored in the previous step are
|
to have problems. Files which were ignored in the previous step are also
|
||||||
also ignored in this step.
|
ignored in this step.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
@ -121,7 +121,8 @@ PostgreSQL documentation
|
|||||||
<title>Options</title>
|
<title>Options</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The following command-line options control the behavior.
|
<application>pg_verifybackup</application> accepts the following
|
||||||
|
command-line arguments:
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -373,7 +373,7 @@ ereport(ERROR,
|
|||||||
specify suppression of the <literal>CONTEXT:</literal> portion of a message in
|
specify suppression of the <literal>CONTEXT:</literal> portion of a message in
|
||||||
the postmaster log. This should only be used for verbose debugging
|
the postmaster log. This should only be used for verbose debugging
|
||||||
messages where the repeated inclusion of context would bloat the log
|
messages where the repeated inclusion of context would bloat the log
|
||||||
volume too much.
|
too much.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
@ -631,8 +631,8 @@ logicalrep_partition_open(LogicalRepRelMapEntry *root,
|
|||||||
/*
|
/*
|
||||||
* If the partition's attributes don't match the root relation's, we'll
|
* If the partition's attributes don't match the root relation's, we'll
|
||||||
* need to make a new attrmap which maps partition attribute numbers to
|
* need to make a new attrmap which maps partition attribute numbers to
|
||||||
* remoterel's, instead the original which maps root relation's attribute
|
* remoterel's, instead of the original which maps root relation's
|
||||||
* numbers to remoterel's.
|
* attribute numbers to remoterel's.
|
||||||
*
|
*
|
||||||
* Note that 'map' which comes from the tuple routing data structure
|
* Note that 'map' which comes from the tuple routing data structure
|
||||||
* contains 1-based attribute numbers (of the parent relation). However,
|
* contains 1-based attribute numbers (of the parent relation). However,
|
||||||
|
@ -1369,7 +1369,7 @@ ProcSleep(LOCALLOCK *locallock, LockMethod lockMethodTable)
|
|||||||
else
|
else
|
||||||
LWLockRelease(ProcArrayLock);
|
LWLockRelease(ProcArrayLock);
|
||||||
|
|
||||||
/* prevent signal from being resent more than once */
|
/* prevent signal from being sent again more than once */
|
||||||
allow_autovacuum_cancel = false;
|
allow_autovacuum_cancel = false;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user