Обсуждение: Typo in event_trigger.c

Hi all,

I just bumped into the following:
--- a/src/backend/commands/event_trigger.c
+++ b/src/backend/commands/event_trigger.c
@@ -742,7 +742,7 @@ EventTriggerCommonSetup(Node *parsetree,

    /*
     * Filter list of event triggers by command tag, and copy them into our
-    * memory context.  Once we start running the command trigers, or indeed
+    * memory context.  Once we start running the command triggers, or indeed
     * once we do anything at all that touches the catalogs, an invalidation
     * might leave cachelist pointing at garbage, so we must do this before we
     * can do much else.

Thanks to David Steele for pointing out a similar typo in one of my patches :p
--
Michael

On Wed, Nov 9, 2016 at 5:35 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> Committed.

Thanks.
-- 
Michael

On Tue, Nov 8, 2016 at 8:28 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Hi all,
>
> I just bumped into the following:
> --- a/src/backend/commands/event_trigger.c
> +++ b/src/backend/commands/event_trigger.c
> @@ -742,7 +742,7 @@ EventTriggerCommonSetup(Node *parsetree,
>
>     /*
>      * Filter list of event triggers by command tag, and copy them into our
> -    * memory context.  Once we start running the command trigers, or indeed
> +    * memory context.  Once we start running the command triggers, or indeed
>      * once we do anything at all that touches the catalogs, an invalidation
>      * might leave cachelist pointing at garbage, so we must do this before we
>      * can do much else.
>
> Thanks to David Steele for pointing out a similar typo in one of my patches :p

Committed.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company