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

Commit4c4aaa1

Browse files
committed
doc: clarify how logical replication takes its initial snapshot
Reported-by: Koen De GrooteDiscussion:https://postgr.es/m/171606613152.686.7693963105919927503@wrigleys.postgresql.orgBackpatch-through: master
1 parent53dcba9 commit4c4aaa1

File tree

1 file changed

+6
-14
lines changed

1 file changed

+6
-14
lines changed

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

Lines changed: 6 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,11 @@
2424
</para>
2525

2626
<para>
27-
Logical replication of a table typically starts with taking a snapshot
28-
of the data on the publisher database and copying that to the subscriber.
29-
Once that is done, the changes on the publisher are sent to the subscriber
30-
as they occur in real-time. The subscriber applies the data in the same
27+
When logical replication of a table typically starts, PostgreSQL takes
28+
a snapshot of the table's data on the publisher database and copies it
29+
to the subscriber. Once complete, changes on the publisher since the
30+
initial copy are sent continually to the subscriber. The subscriber
31+
applies the data in the same
3132
order as the publisher so that transactional consistency is guaranteed for
3233
publications within a single subscription. This method of data replication
3334
is sometimes referred to as transactional replication.
@@ -165,7 +166,7 @@
165166
The individual tables can be added and removed dynamically using
166167
<link linkend="sql-alterpublication"><command>ALTER PUBLICATION</command></link>. Both the <literal>ADD
167168
TABLE</literal> and <literal>DROP TABLE</literal> operations are
168-
transactional; so the table will start or stop replicating at the correct
169+
transactional, so the table will start or stop replicating at the correct
169170
snapshot once the transaction has committed.
170171
</para>
171172
</sect1>
@@ -1954,15 +1955,6 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
19541955
<sect1 id="logical-replication-architecture">
19551956
<title>Architecture</title>
19561957

1957-
<para>
1958-
Logical replication starts by copying a snapshot of the data on the
1959-
publisher database. Once that is done, changes on the publisher are sent
1960-
to the subscriber as they occur in real time. The subscriber applies data
1961-
in the order in which commits were made on the publisher so that
1962-
transactional consistency is guaranteed for the publications within any
1963-
single subscription.
1964-
</para>
1965-
19661958
<para>
19671959
Logical replication is built with an architecture similar to physical
19681960
streaming replication (see <xref linkend="streaming-replication"/>). It is

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp