Re: non-bulk inserts and tuple routing

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: non-bulk inserts and tuple routing
Date: 2018-02-09 10:26:01
Message-ID: 5A7D7739.40001@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(2018/02/08 23:21), Robert Haas wrote:
> On Thu, Feb 8, 2018 at 5:16 AM, Etsuro Fujita
> <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> if (resultRelInfo == NULL);
>> {
>> /* Initialize partition info. */
>> resultRelInfo = ExecInitPartitionInfo(mtstate,
>> saved_resultRelInfo,
>> proute,
>> estate,
>> leaf_part_index);
>> }
>
> I'm pretty sure that code has one semicolon too many.

Good catch!

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2018-02-09 11:02:45 Re: Using scalar function as set-returning: bug or feature?
Previous Message Etsuro Fujita 2018-02-09 10:24:15 Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly