diff options
| author | Amit Kapila | 2023-06-22 07:07:19 +0000 |
|---|---|---|
| committer | Amit Kapila | 2023-06-22 07:07:19 +0000 |
| commit | f5c446e3367527f9db1506d7c38d2f56e20950b6 (patch) | |
| tree | fd8ede2d317f33600993da0b4cad999bf6f5527e | |
| parent | c2d35bb88eab99fd81198fa4caee004fb8997c73 (diff) | |
Doc: Clarify the behavior of triggers/rules in a logical subscriber.
By default, triggers and rules do not fire on a logical replication
subscriber based on the "session_replication_role" GUC being set to
"replica". However, the docs in the logical replication section assumed
that the reader understood how this GUC worked. This modifies the docs to
be more explicit and links back to the GUC itself.
Author: Jonathan Katz, Peter Smith
Reviewed-by: Vignesh C, Euler Taveira
Backpatch-through: 11
Discussion: https://postgr.es/m/[email protected]
| -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 59cf92e6a9..aeab39626d 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> |