Skip to content

Commit 5b0c46e

Browse files
author
Amit Kapila
committed
Doc: Update the behavior of generated columns in Logical Replication.
Commit 745217a misses updating the new behavior of generated columns in logical replication at a few places. Reported-by: Peter Smith, Ajin Cherian Author: Vignesh C Discussion: https://postgr.es/m/CALDaNm2JOO7szz9+uaQbjmgZOfzbM_9tAQdFF8H5BjkQeaJs0A@mail.gmail.com Discussion: https://postgr.es/m/B80D17B2-2C8E-4C7D-87F2-E5B4BE3C069E@gmail.com
1 parent 027124a commit 5b0c46e

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

doc/src/sgml/ddl.sgml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -514,8 +514,9 @@ CREATE TABLE people (
514514
</listitem>
515515
<listitem>
516516
<para>
517-
Generated columns are skipped for logical replication and cannot be
518-
specified in a <command>CREATE PUBLICATION</command> column list.
517+
Generated columns can be replicated during logical replication by
518+
including them in the column list of the
519+
<command>CREATE PUBLICATION</command> command.
519520
</para>
520521
</listitem>
521522
</itemizedlist>

doc/src/sgml/logical-replication.sgml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1436,7 +1436,9 @@ test_sub=# SELECT * FROM child ORDER BY a;
14361436
During initial data synchronization, only the published columns are
14371437
copied. However, if the subscriber is from a release prior to 15, then
14381438
all the columns in the table are copied during initial data synchronization,
1439-
ignoring any column lists.
1439+
ignoring any column lists. If the subscriber is from a release prior to 18,
1440+
then initial table synchronization won't copy generated columns even if they
1441+
are defined in the publisher.
14401442
</para>
14411443

14421444
<warning id="logical-replication-col-list-combining">

0 commit comments

Comments
 (0)