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 1jLmIv-0003o0-6K for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Apr 2020 11:22:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jLmIt-00085q-Fo for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Apr 2020 11:22:03 +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 1jLmIt-00085f-9t; Tue, 07 Apr 2020 11:22:03 +0000 Received: from mail.thelabyrinth.net ([45.56.70.56]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jLmIq-0002wD-9x; Tue, 07 Apr 2020 11:22:01 +0000 Received: from Davids-MacBook-Pro.local (c-73-39-102-148.hsd1.va.comcast.net [73.39.102.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: dsteele) by mail.thelabyrinth.net (Postfix) with ESMTPSA id 2F7685467B; Tue, 7 Apr 2020 11:21:59 +0000 (UTC) Subject: Re: Don't try fetching future segment of a TLI. To: Kyotaro Horiguchi , masao.fujii@oss.nttdata.com 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> From: David Steele Message-ID: <4a461c7b-b90a-6644-64a6-80eac69c27bc@pgmasters.net> Date: Tue, 7 Apr 2020 07:21:58 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200407.164801.1830442317313243264.horikyota.ntt@gmail.com> 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 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. -- -David david@pgmasters.net