Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oQMvm-0007lE-1j for pgsql-hackers@arkaria.postgresql.org; Tue, 23 Aug 2022 05:58:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oQMvk-00081v-UU for pgsql-hackers@arkaria.postgresql.org; Tue, 23 Aug 2022 05:58:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oQMvk-00081m-Fx for pgsql-hackers@lists.postgresql.org; Tue, 23 Aug 2022 05:58:28 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oQMvh-0002Nj-Ey for pgsql-hackers@postgresql.org; Tue, 23 Aug 2022 05:58:27 +0000 Received: from [192.168.8.251] (unknown [93.174.131.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id AA27221C33A7; Tue, 23 Aug 2022 08:58:22 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1661234302; bh=0NrdsgcH6BIqlvKpp1u9cyVgGSOr2UMK/OZNygnHL2E=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=CPqL3AKLEF8jos7k0QX301klKd6b2X86Q/YHSAF8NiR4JxfovEW0bMoa1w1v9Ykv7 KE9RGtMQKmtwKdRqVQwBySBsppa/YJ8DXpIxd4EGkpjWix9i3fBGgbGxIpV9Icf0mk sxtFzNwgl1cg7lLibxgWMy3JqOIe8zBmqB8nk60w= Message-ID: <30b35bf3-6bfc-c52c-cccf-aec3d5f6e76d@postgrespro.ru> Date: Tue, 23 Aug 2022 08:58:22 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: Fast COPY FROM based on batch insert Content-Language: en-US To: Etsuro Fujita Cc: Justin Pryzby , Zhihong Yu , Amit Langote , tanghy.fnst@fujitsu.com, Ashutosh Bapat , Pg Hackers , Tomas Vondra , houzj.fnst@fujitsu.com References: <45ad1b94-339b-a841-8885-67ebe6fc5bc1@postgrespro.ru> <57733596-5fd6-07ec-d65c-67411411f10e@postgrespro.ru> <05bc8819-3e53-d884-a0d0-a17ffa5febef@postgrespro.ru> <09ff35ff-291f-d9e9-a0ed-55e6bb9732fc@postgrespro.ru> <9b293a07-c822-a326-6ff2-4a9e0e9e5549@postgrespro.ru> From: Andrey Lepikhov Organization: Postgres Professional In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 22/8/2022 11:44, Etsuro Fujita wrote: > I think the latter is more consistent with the existing error context > information when in CopyMultiInsertBufferFlush(). Actually, I thought > this too, and I think this would be useful when the COPY FROM command > is executed on a foreign table. My concern, however, is the case when > the command is executed on a partitioned table containing foreign > partitions; in that case the input data would not always be sorted in > the partition order, so the range for an error-occurring foreign > partition might contain many lines with rows from other partitions, > which I think makes the range information less useful. Maybe I'm too > worried about that, though. I got your point. Indeed, perharps such info doesn't really needed to be included into the core, at least for now. -- regards, Andrey Lepikhov Postgres Professional