Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit3470391

Browse files
author
Amit Kapila
committed
Doc: Fix ambuiguity in column lists.
The behavior for columns added later to the table for publications with nospecified column lists was not clear.Reported-by: Koen De GrooteAuthor: Peter SmithReviewed-by: Vignesh C, Laurenz AlbeBackpatch-through: 15Discussion:https://postgr.es/m/171621878740.686.11325940592820985181@wrigleys.postgresql.org
1 parentc50d4f4 commit3470391

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎doc/src/sgml/logical-replication.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1382,9 +1382,9 @@ test_sub=# SELECT * FROM child ORDER BY a;
13821382
</para>
13831383

13841384
<para>
1385-
If no column list is specified, any columns added later are automatically
1386-
replicated. This means that having a column list which names all columns
1387-
is not the same as having no column list at all.
1385+
If no column list is specified, any columns addedto the tablelater are
1386+
automaticallyreplicated. This means that having a column list which names
1387+
all columnsis not the same as having no column list at all.
13881388
</para>
13891389

13901390
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp