diff options
| -rw-r--r-- | doc/src/sgml/logical-replication.sgml | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 59cf92e6a91..aeab39626d6 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -1654,9 +1654,13 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER <para> The apply process on the subscriber database always runs with - <varname>session_replication_role</varname> set - to <literal>replica</literal>, which produces the usual effects on triggers - and constraints. + <link linkend="guc-session-replication-role"><varname>session_replication_role</varname></link> + set to <literal>replica</literal>. This means that, by default, + triggers and rules will not fire on a subscriber. Users can optionally choose to + enable triggers and rules on a table using the + <link linkend="sql-altertable"><command>ALTER TABLE</command></link> command + and the <literal>ENABLE TRIGGER</literal> and <literal>ENABLE RULE</literal> + clauses. </para> <para> |