mirror of
https://github.com/postgres/postgres.git
synced 2025-10-25 13:17:41 +03:00
doc: Fix some grammar and inconsistent tags
Author: Ekaterina Kiryanova, Elena Indrupskaya, Oleg Sibiryakov, Maxim Yablokov Discussion: https://postgr.es/m/4c2a430b-32e2-44e2-aeca-03b7db6824e4@postgrespro.ru
This commit is contained in:
@@ -326,11 +326,12 @@ postgres=# select * from pg_logical_slot_get_changes('regression_slot', NULL, NU
|
||||
will work but only while the connection is alive (for example a node
|
||||
restart would break it). Then, the primary may delete system catalog rows
|
||||
that could be needed by the logical decoding on the standby (as it does
|
||||
not know about the catalog_xmin on the standby). Existing logical slots
|
||||
on standby also get invalidated if <varname>wal_level</varname> on the
|
||||
primary is reduced to less than <literal>logical</literal>.
|
||||
not know about the <literal>catalog_xmin</literal> on the standby).
|
||||
Existing logical slots on standby also get invalidated if
|
||||
<varname>wal_level</varname> on the primary is reduced to less than
|
||||
<literal>logical</literal>.
|
||||
This is done as soon as the standby detects such a change in the WAL stream.
|
||||
It means that, for walsenders which are lagging (if any), some WAL records up
|
||||
It means that, for walsenders that are lagging (if any), some WAL records up
|
||||
to the <varname>wal_level</varname> parameter change on the primary won't be
|
||||
decoded.
|
||||
</para>
|
||||
|
||||
Reference in New Issue
Block a user