summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDaniele Varrazzo <daniele.varrazzo@gmail.com>2019-04-01 10:47:56 +0100
committerDaniele Varrazzo <daniele.varrazzo@gmail.com>2019-04-01 10:54:01 +0100
commit544e1576490449253f104c8601871b7958498a1e (patch)
treea2f1ef8b268ff2d57ea3c745ecf2e8b9038d77f8 /doc
parented74189acdcff99e3ec00ba1ec7f016da3f700fb (diff)
downloadpsycopg2-544e1576490449253f104c8601871b7958498a1e.tar.gz
Fixed replication cursor docs warning indentation level
Diffstat (limited to 'doc')
-rw-r--r--doc/src/extras.rst20
1 files changed, 9 insertions, 11 deletions
diff --git a/doc/src/extras.rst b/doc/src/extras.rst
index 59fdf35..5d09039 100644
--- a/doc/src/extras.rst
+++ b/doc/src/extras.rst
@@ -512,17 +512,15 @@ The individual messages in the replication stream are represented by
except InterruptedError:
pass # recalculate timeout and continue
- .. warning::
-
- The ``consume({msg})`` function will only be called when
- there are new database writes on the server e.g. any DML or
- DDL statement. Depending on your Postgres cluster
- configuration this might cause the server to run out of disk
- space if the writes are far apart. To prevent this from
- happening you can use `~ReplicationCursor.wal_end` value to
- periodically send feedback to the server to notify that your
- replication client has received and processed all the
- messages.
+.. warning::
+
+ The :samp:`consume({msg})` function will only be called when there are new
+ database writes on the server e.g. any DML or DDL statement. Depending on
+ your Postgres cluster configuration this might cause the server to run out
+ of disk space if the writes are too far apart. To prevent this from
+ happening you can use `~ReplicationCursor.wal_end` value to periodically
+ send feedback to the server to notify that your replication client has
+ received and processed all the messages.
.. index::