mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-02-23 19:39:53 +08:00
doc: Document some nuances of logical replication of TRUNCATE
This commit is contained in:
parent
8121ab88e7
commit
c9d6a45724
@ -371,6 +371,22 @@
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Replication of <command>TRUNCATE</command> commands is supported, but
|
||||
some care must be taken when truncating groups of tables connected by
|
||||
foreign keys. When replicating a truncate action, the subscriber will
|
||||
truncate the same group of tables that was truncated on the publisher,
|
||||
either explictly specified or implicitly collected via
|
||||
<literal>CASCADE</literal>, minus tables that are not part of the
|
||||
subscription. This will work correctly if all affected tables are part
|
||||
of the same subscription. But if some tables to be truncated on the
|
||||
subscriber have foreign-key links to tables that are not part of the same
|
||||
(or any) subscription, then the application of the truncate action on the
|
||||
subscriber will fail.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Large objects (see <xref linkend="largeobjects"/>) are not replicated.
|
||||
|
Loading…
Reference in New Issue
Block a user