fix typo

diff --git a/src/test/regress/expected/triggers.out b/src/test/regress/expected/triggers.out
index 6d8a436f5001ac0fb09b963ea61ab7627604ed4d..d8b0594c2bd8be7dd9be17bba5d79ccf1c127b44 100644 (file)
--- a/src/test/regress/expected/triggers.out
+++ b/src/test/regress/expected/triggers.out
@@ -403,7 +403,7 @@ begin
 
    relid := TG_relid::regclass;
 
-   -- plpgsql can't discover it's trigger data in a hash like perl and python
+   -- plpgsql can't discover its trigger data in a hash like perl and python
    -- can, or by a sort of reflection like tcl can, 
    -- so we have to hard code the names.
    raise NOTICE 'TG_NAME: %', TG_name;
@@ -433,6 +433,7 @@ begin
    if TG_OP != 'DELETE' then
        raise NOTICE 'NEW: %', NEW;
    end if;
+
    if TG_OP = 'DELETE' then
        return OLD;
    else

diff --git a/src/test/regress/sql/triggers.sql b/src/test/regress/sql/triggers.sql
index fc688a08f9c75720ed9df020b3082d402c393e2c..909a7d68d9be28cc7791589a50f2e45d00fdd35b 100644 (file)
--- a/src/test/regress/sql/triggers.sql
+++ b/src/test/regress/sql/triggers.sql
@@ -314,7 +314,7 @@ begin
 
    relid := TG_relid::regclass;
 
-   -- plpgsql can't discover it's trigger data in a hash like perl and python
+   -- plpgsql can't discover its trigger data in a hash like perl and python
    -- can, or by a sort of reflection like tcl can, 
    -- so we have to hard code the names.
    raise NOTICE 'TG_NAME: %', TG_name;
@@ -344,6 +344,7 @@ begin
    if TG_OP != 'DELETE' then
        raise NOTICE 'NEW: %', NEW;
    end if;
+
    if TG_OP = 'DELETE' then
        return OLD;
    else