aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/tablecmds.c
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2023-06-22 12:37:19 +0530
committerAmit Kapila <akapila@postgresql.org>2023-06-22 12:37:19 +0530
commitf5c446e3367527f9db1506d7c38d2f56e20950b6 (patch)
treefd8ede2d317f33600993da0b4cad999bf6f5527e /src/backend/commands/tablecmds.c
parentc2d35bb88eab99fd81198fa4caee004fb8997c73 (diff)
downloadpostgresql-f5c446e3367527f9db1506d7c38d2f56e20950b6.tar.gz
postgresql-f5c446e3367527f9db1506d7c38d2f56e20950b6.zip
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/5bb2c9a2-499f-e1a2-6e33-5ce96b35cc4a@postgresql.org
Diffstat (limited to 'src/backend/commands/tablecmds.c')
0 files changed, 0 insertions, 0 deletions