Fix some grammar and typos in comments and docs
The documentation fixes are backpatched down to where they apply. Author: Justin Pryzby Discussion: https://postgr.es/m/20201031020801.GD3080@telsasoft.com Backpatch-through: 9.6
This commit is contained in:
parent
0a593bc467
commit
c7f41b2999
|
@ -3324,7 +3324,7 @@ CREATE INDEX ON measurement (logdate);
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Normally the set of partitions established when initially defining the
|
Normally the set of partitions established when initially defining the
|
||||||
table are not intended to remain static. It is common to want to
|
table is not intended to remain static. It is common to want to
|
||||||
remove old partitions of data and periodically add new partitions for
|
remove old partitions of data and periodically add new partitions for
|
||||||
new data. One of the most important advantages of partitioning is
|
new data. One of the most important advantages of partitioning is
|
||||||
precisely that it allows this otherwise painful task to be executed
|
precisely that it allows this otherwise painful task to be executed
|
||||||
|
|
|
@ -71,7 +71,7 @@ PostgreSQL documentation
|
||||||
copied from the WAL archive to the <filename>pg_wal</filename> directory, or
|
copied from the WAL archive to the <filename>pg_wal</filename> directory, or
|
||||||
fetched on startup by configuring <filename>recovery.conf</filename>. The use of
|
fetched on startup by configuring <filename>recovery.conf</filename>. The use of
|
||||||
<application>pg_rewind</application> is not limited to failover, e.g., a standby
|
<application>pg_rewind</application> is not limited to failover, e.g., a standby
|
||||||
server can be promoted, run some write transactions, and then rewinded
|
server can be promoted, run some write transactions, and then rewound
|
||||||
to become a standby again.
|
to become a standby again.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue