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 1jLkef-00076T-D3 for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Apr 2020 09:36:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jLkee-00067v-43 for pgsql-bugs@arkaria.postgresql.org; Tue, 07 Apr 2020 09:36:24 +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 1jLked-00067o-Ru for pgsql-bugs@lists.postgresql.org; Tue, 07 Apr 2020 09:36:23 +0000 Received: from cyclops.postgrespro.ru ([93.174.131.138] helo=mail.postgrespro.ru) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jLkea-0003dS-Vr for pgsql-bugs@lists.postgresql.org; Tue, 07 Apr 2020 09:36:23 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 4872621C595C for ; Tue, 7 Apr 2020 12:36:19 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=x tagged_above=-99 required=4 WHITELISTED tests=[] autolearn=unavailable Received: from [192.168.3.128] (broadband-95-84-150-205.ip.moscow.rt.ru [95.84.150.205]) (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 CD14821C595A for ; Tue, 7 Apr 2020 12:36:18 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1586252178; bh=6CrRbAfhLbe4YNa4O34mFNn+B5qiX1RaHl/+haJiB0M=; h=Subject:To:References:From:Date:In-Reply-To; b=dBTImWXjQBplD4d1myyFLzHTeHoB/tdvMl8lGky34S2A+KFZO1OHvassYyLSUk/6q xtPh2gI8VROmmA68xsHYiPhQw/svrPLKDMPUJ5M+VeE97sBQtDxF3/wTvAX8VlZQqM H+KuTIJ/Fd+OzGtX0UFsE5Vjflf+0SYEJSc+37UA= Subject: Re: Don't try fetching future segment of a TLI. To: pgsql-bugs@lists.postgresql.org References: <16159-f5a34a3a04dc67e0@postgresql.org> <20191212.124856.202839248708529678.horikyota.ntt@gmail.com> <20200129.120222.1476610231001551715.horikyota.ntt@gmail.com> <8c831a30-a3a2-de89-2059-e7ce842d7aed@pgmasters.net> <792ea085-95c4-bca0-ae82-47fdc80e146d@oss.nttdata.com> <762ffb60-df9c-0efc-2714-9859219157e3@pgmasters.net> <3e0713d2-56d2-9883-4213-d5ba7f0dcabf@oss.nttdata.com> <20200407081732.GC6655@paquier.xyz> From: Grigory Smolkin Message-ID: Date: Tue, 7 Apr 2020 12:36:18 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20200407081732.GC6655@paquier.xyz> Content-Type: multipart/alternative; boundary="------------64E2721A0DCEEC577AD1DB9F" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------64E2721A0DCEEC577AD1DB9F Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I`ve bumped into this issue recently: https://www.postgresql.org/message-id/dd6690b0-ec03-6b3c-6fac-c963f91f87a7%40postgrespro.ru On 4/6/20 8:43 PM, Fujii Masao wrote: > The patch looks good to me. Attached is the updated version of the patch. > I updated only comments. > > Barring any objection, I will commit this patch. I`ve been running tests on your patch. So far so good. On Tue, Apr 07, 2020 at 12:15:00PM +0900, Fujii Masao wrote: > 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 to back-patching it. -- Grigory Smolkin Postgres Professional: http://www.postgrespro.com The Russian Postgres Company --------------64E2721A0DCEEC577AD1DB9F Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit

I`ve bumped into this issue recently:
https://www.postgresql.org/message-id/dd6690b0-ec03-6b3c-6fac-c963f91f87a7%40postgrespro.ru


On 4/6/20 8:43 PM, Fujii Masao wrote:

The patch looks good to me. Attached is the updated version of the patch.
I updated only comments.

Barring any objection, I will commit this patch.

I`ve been running tests on your patch. So far so good.

On Tue, Apr 07, 2020 at 12:15:00PM +0900, Fujii Masao wrote:
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 to back-patching it.

-- 
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--------------64E2721A0DCEEC577AD1DB9F--