diff options
| author | Tom Lane | 2025-06-05 19:24:15 +0000 |
|---|---|---|
| committer | Tom Lane | 2025-06-05 19:24:15 +0000 |
| commit | c37be39a74b25cc9c7b052ddae43061a6a2c6019 (patch) | |
| tree | 330649591de48359c7aa8147cf594e741cbbd5a4 | |
| parent | 54c6ea8c81db718508eeea50991d3c1c5dff54a5 (diff) | |
Refine wording from commit 01463e1cc.
Author: Noah Misch <noah@leadboat.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/20250605163441.2f.nmisch@google.com
| -rw-r--r-- | doc/src/sgml/trigger.sgml | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml index e9214dcf1b1..bb1b5faf34e 100644 --- a/doc/src/sgml/trigger.sgml +++ b/doc/src/sgml/trigger.sgml @@ -129,10 +129,9 @@ In all cases, a trigger is executed as part of the same transaction as the statement that triggered it, so if either the statement or the trigger causes an error, the effects of both will be rolled back. - Also, the trigger will always run in the security context of the role - that executed the statement that caused the trigger to fire, unless - the trigger function is defined as <literal>SECURITY DEFINER</literal>, - in which case it will run as the function owner. + Also, the trigger will always run as the role that queued the trigger + event, unless the trigger function is marked as <literal>SECURITY + DEFINER</literal>, in which case it will run as the function owner. </para> <para> |