Re: Multi-insert related comment in CopyFrom()

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Multi-insert related comment in CopyFrom()
Date: 2022-09-22 07:11:29
Message-ID: CAPmGK15EUXqLRc8nzjxgJz4qZgpBoUP_89otQvLTPSV=M0JYSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 21, 2022 at 4:39 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

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