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 1jLrPu-0007lZ-L3 for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Apr 2020 16:49:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jLrPt-0001PK-IH for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Apr 2020 16:49:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jLrPt-0001P9-C5; Tue, 07 Apr 2020 16:49:37 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jLrPp-0007BJ-So; Tue, 07 Apr 2020 16:49:37 +0000 Received: from hnk.local (p2421237-ipbf2725funabasi.chiba.ocn.ne.jp [122.24.33.237]) by oss.nttdata.com (Postfix) with ESMTPSA id AFE736033A; Wed, 8 Apr 2020 01:49:27 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.2 at oss.nttdata.com Subject: Re: Don't try fetching future segment of a TLI. To: David Steele , Kyotaro Horiguchi Cc: psuderevsky@gmail.com, pgsql-hackers@lists.postgresql.org, pgsql-bugs@lists.postgresql.org References: <792ea085-95c4-bca0-ae82-47fdc80e146d@oss.nttdata.com> <762ffb60-df9c-0efc-2714-9859219157e3@pgmasters.net> <3e0713d2-56d2-9883-4213-d5ba7f0dcabf@oss.nttdata.com> <20200407.164801.1830442317313243264.horikyota.ntt@gmail.com> <4a461c7b-b90a-6644-64a6-80eac69c27bc@pgmasters.net> From: Fujii Masao Message-ID: <21d2590f-2739-9f45-748f-7a68d667d7cd@oss.nttdata.com> Date: Wed, 8 Apr 2020 01:49:27 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <4a461c7b-b90a-6644-64a6-80eac69c27bc@pgmasters.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020/04/07 20:21, David Steele wrote: > > On 4/7/20 3:48 AM, Kyotaro Horiguchi wrote: >> At Tue, 7 Apr 2020 12:15:00 +0900, Fujii Masao wrote in >>>>> This doesn't seem a bug, so I'm thinking to merge this to next *major* >>>>> version release, i.e., v13. >>>> Not a bug, perhaps, but I think we do consider back-patching >>>> performance problems. The rise in S3 usage has just exposed how poorly >>>> this performed code in high-latency environments. >>> >>> I understood the situation and am fine to back-patch that. But I'm not >>> sure >>> if it's fair to do that. Maybe we need to hear more opinions about >>> this? >>> OTOH, feature freeze for v13 is today, so what about committing the >>> patch >>> in v13 at first, and then doing the back-patch after hearing opinions >>> and >>> receiving many +1? >> >> +1 for commit only v13 today, then back-patch if people wants and/or >> accepts. > > Definitely +1 for a commit today to v13. I certainly was not trying to hold that up Pushed the patch to v13, at first! Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION