aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-04-21 15:33:25 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-04-21 15:33:25 -0400
commitc29a752c683d9b08ee1376709b825532e94c2709 (patch)
treed9a99c3ac4e1c5b3df5d1d5c9898cd2a484788cb
parent536d47bd9d5fce8d91929bee3128fa1d08dbcc57 (diff)
downloadpostgresql-c29a752c683d9b08ee1376709b825532e94c2709.tar.gz
postgresql-c29a752c683d9b08ee1376709b825532e94c2709.zip
doc: Fix typo
-rw-r--r--doc/src/sgml/logical-replication.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 7bfff24a68f..e7526905f8c 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -24,7 +24,7 @@
</para>
<para>
- Logical replication of a table typically starts with a taking a snapshot
+ Logical replication of a table typically starts with taking a snapshot
of the data on the publisher database and copying that to the subscriber.
Once that is done, the changes on the publisher are sent to the subscriber
as they occur in real-time. The subscriber applies the data in the same