summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-07-08 14:28:42 +0200
committerPeter Eisentraut <peter@eisentraut.org>2019-07-08 14:29:11 +0200
commita5407d1bd6286c0f932514b8dc58f472981e0243 (patch)
treebac6c2a362296b1b3e2d1331608088d36166e97b
parent232019b79229db7a438f00f358d86659fbd6fcb9 (diff)
doc: Clarify logical replication documentation
Document that the data types of replicated tables do not need to match. The documentation previously claimed that they had to match. Author: Robert Treat <rob@xzilla.net> Discussion: https://www.postgresql.org/message-id/flat/CAJSLCQ13==D8Ka2YLyctTm0Y+8MhGYcX_zj7fU0rqRzhcV++3w@mail.gmail.com
-rw-r--r--doc/src/sgml/logical-replication.sgml13
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 41770a466c8..0f0fb00bc9f 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -232,10 +232,15 @@
</para>
<para>
- Columns of a table are also matched by name. A different order of columns
- in the target table is allowed, but the column types have to match. The
- target table can have additional columns not provided by the published
- table. Those will be filled with their default values.
+ Columns of a table are also matched by name. The order of columns in the
+ subscriber table does not need to match that of the publisher. The data
+ types of the columns do not need to match, as long as the text
+ representation of the data can be converted to the target type. For
+ example, you can replicate from a column of type <type>integer</type> to a
+ column of type <type>bigint</type>. The target table can also have
+ additional columns not provided by the published table. Any such columns
+ will be filled with the default value as specified in the definition of the
+ target table.
</para>
<sect2 id="logical-replication-subscription-slot">