Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1egS8G-0007F5-CB for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Jan 2018 09:23:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1egS8F-00085k-9H for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Jan 2018 09:23:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1egS8F-00085b-2Z for pgsql-hackers@lists.postgresql.org; Tue, 30 Jan 2018 09:23:11 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1egS87-0004GB-OO for pgsql-hackers@lists.postgresql.org; Tue, 30 Jan 2018 09:23:10 +0000 Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id w0U9N19j000500 for ; Tue, 30 Jan 2018 18:23:01 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 0BFA960292; Tue, 30 Jan 2018 18:23:01 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 001005F592; Tue, 30 Jan 2018 18:23:00 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.241.75]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id F04624005E7; Tue, 30 Jan 2018 18:23:00 +0900 (JST) Message-ID: <5A70396A.8090400@lab.ntt.co.jp> Date: Tue, 30 Jan 2018 18:22:50 +0900 From: Etsuro Fujita User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 Subject: Re: non-bulk inserts and tuple routing References: <8975331d-d961-cbdd-f862-fdd3d97dc2d0@lab.ntt.co.jp> <56c9f77b-830c-4652-233e-a1c5fa5a9938@lab.ntt.co.jp> <8f53a342-e0df-4fc9-7422-c3c3c601117c@lab.ntt.co.jp> <5A69A3B7.10403@lab.ntt.co.jp> <37f7cc10-def8-b2d0-615d-dfe035e7b1ee@lab.ntt.co.jp> In-Reply-To: <37f7cc10-def8-b2d0-615d-dfe035e7b1ee@lab.ntt.co.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Amit Langote Cc: pgsql-hackers@lists.postgresql.org X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk (2018/01/25 18:52), Amit Langote wrote: > On 2018/01/25 18:30, Etsuro Fujita wrote: >> The patches apply cleanly and compile successfully, but make check fails >> in an assert-enabled build. > > Hmm, I can't seem to reproduce the failure with v4 patches I posted > earlier today. > Can you please post the errors you're seeing? A quick debug showed that the failure was due to a segmentation fault caused by this change to ExecSetupPartitionTupleRouting (in patch v4-0003-During-tuple-routing-initialize-per-partition-obj): - bool is_update = false; + bool is_update; I modified that patch to initialize the is_update to false as before. With the modified version, make check passed successfully. I'll review the patch in more detail! Best regards, Etsuro Fujita