postgres.git / summary / log / commit / refs

commit    eab30cc6b55dc03589bda13bc76b12d7142d5686
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Wed Jan 31 22:52:47 2018 +0000
First released in: 11.0, 10.2

    doc:  fix trigger inheritance wording
    
    Fix wording from commit 1cf1112990cff432b53a74a0ac9ca897ce8a7688
    
    Reported-by: Robert Haas
    
    Backpatch-through: 10


 doc/src/sgml/ref/create_trigger.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
index dab10411302..3d6b9f033c1 100644
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ b/doc/src/sgml/ref/create_trigger.sgml
@@ -503,7 +503,7 @@ UPDATE OF <replaceable>column_name1</replaceable> [, <replaceable>column_name2</
    Modifying a partitioned table or a table with inheritance children fires
    statement-level triggers attached to the explicitly named table, but not
    statement-level triggers for its partitions or child tables.  In contrast,
-   row-level triggers are fired on the rows in effected partitions or
+   row-level triggers are fired on the rows in affected partitions or
    child tables, even if they are not explicitly named in the query.
    If a statement-level trigger has been defined with transition relations
    named by a <literal>REFERENCING</literal> clause, then before and after


[parent: 59ad24635076]