Fixed replication cursor docs warning indentation level

This commit is contained in:
Daniele Varrazzo 2019-04-01 10:47:56 +01:00
parent ed74189acd
commit 544e157649

View File

@ -512,17 +512,15 @@ The individual messages in the replication stream are represented by
except InterruptedError: except InterruptedError:
pass # recalculate timeout and continue pass # recalculate timeout and continue
.. warning:: .. warning::
The ``consume({msg})`` function will only be called when The :samp:`consume({msg})` function will only be called when there are new
there are new database writes on the server e.g. any DML or database writes on the server e.g. any DML or DDL statement. Depending on
DDL statement. Depending on your Postgres cluster your Postgres cluster configuration this might cause the server to run out
configuration this might cause the server to run out of disk of disk space if the writes are too far apart. To prevent this from
space if the writes are far apart. To prevent this from happening you can use `~ReplicationCursor.wal_end` value to periodically
happening you can use `~ReplicationCursor.wal_end` value to send feedback to the server to notify that your replication client has
periodically send feedback to the server to notify that your received and processed all the messages.
replication client has received and processed all the
messages.
.. index:: .. index::