Re: Multi-insert related comment in CopyFrom() - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: Multi-insert related comment in CopyFrom()
Date
Msg-id CAPmGK15EUXqLRc8nzjxgJz4qZgpBoUP_89otQvLTPSV=M0JYSg@mail.gmail.com
Whole thread Raw
In response to Multi-insert related comment in CopyFrom()  (Etsuro Fujita <etsuro.fujita@gmail.com>)
List pgsql-hackers
On Wed, Sep 21, 2022 at 4:39 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> While working on the “Fast COPY FROM based on batch insert” patch, I
> noticed this:
>
>     else if (proute != NULL && resultRelInfo->ri_TrigDesc != NULL &&
>              resultRelInfo->ri_TrigDesc->trig_insert_new_table)
>     {
>         /*
>          * For partitioned tables we can't support multi-inserts when there
>          * are any statement level insert triggers. It might be possible to
>          * allow partitioned tables with such triggers in the future, but for
>          * now, CopyMultiInsertInfoFlush expects that any before row insert
>          * and statement level insert triggers are on the same relation.
>          */
>         insertMethod = CIM_SINGLE;
>     }
>
> I think there is a thinko in the comment; “before” should be after.
> Patch attached.

Pushed.

Best regards,
Etsuro Fujita



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Schema variables - new implementation for Postgres 15
Next
From: Michael Paquier
Date:
Subject: Re: Refactor backup related code (was: Is it correct to say, "invalid data in file \"%s\"", BACKUP_LABEL_FILE in do_pg_backup_stop?)